| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| mchehab | lja: what demod you're using?
I don't remember any supporting both dvb-s and dvb-t/c a demod supporting both can indeed be a problem, as the frequency range is different... in the case you're talking about, application should first switch the delivery system, and only after that send the dish settings the application sequence should be: switch the delivery system; query the frontend (for the frequency ranges); | [11:14] |
| lja | yes, I just noticed that | [11:20] |
| mchehab | send the diseqc/tone/voltage
and then tune | [11:20] |
| lja | use set_property for DTV_DELIVERY_SYSTEM
but the frequencies are still a problem because they are in different units | [11:21] |
| mchehab | what's the demod you're using on your tests? | [11:22] |
| Haxxa | What do you guys think of this idea - a universal remote with an epaper display? Why? Because LCDs draw a lot of power and you can easy create a low powered tv remote with a customizable layout.. only want the channel buttons and the volume buttons ... sure want a large stand by button - why not? Its a niche market but I think its a lot bettter solution than logitechs harmony remotes... - mockup (http://i.imgur.com/ULTv0JS.jpg) | [11:34] |
| ......... (idle for 42mn) | ||
| crope | mchehab: there is few of those demod, for example those new Silicon Labs ones released year or two ago. they support in practise all dvb standards | [12:16] |
| mchehab | crope: thanks! I think we'll need to do some changes at the dvb core to cover such demods | [12:17] |
| crope | mchehab: just looked the Si216x family which is 2 years old
not sure if that new sony series was also one | [12:18] |
| mchehab | crope, lja: just sent a patch
with such patch, if a demod supports both DVB-S and DVB-C, it will return the range on the right scale, depending on the current delivery system... e. g. if the demod is in DVB-C, it will return the frequency ranges in Hz; if the demod is in DVB-S, it will return the frequency ranges in kHz (compile-tested only) if we decide to apply this patch, it likely makes sense to also change the drivers to receive the tuning frequency and bandwidth in Hz I didn't mark as such, but this patch is RFC | [12:31] |
| crope | patch idea is fine. and also it is good idea to convert DVB-S/S2 frequency to Hz | [12:36] |
| mchehab | eventually, we may add a DTV_FREQUENCY_HZ property and deprecate DTV_FREQUENCY
not sure this could make sense only if we also replace FE_GET_INFO with actually makes sense for other reasons... there are already two deprecated fields there (type and notifier_delay) and enum fe_caps is not capable of describing what's supported or not for newer standards and there's no bits left there s/there's no/there aren't/ | [12:41] |
| ............. (idle for 1h3mn) | ||
| lja | mchehab: that patch doesn't touch the tuners. does it mean that dvb-s/s2 tuner drivers will be kept with khz as units? | [13:51] |
| mchehab | lja: this is RFC
more things need to be changed | [13:51] |
| lja | ah, ok | [13:52] |
| crope | you will need to change tuners too. iirc limits are compared from both tuner and demod, then min/max is taken. if tuner min is 100 and demod min 200, then 100 is used by dvb core
ugh, then 200 is used | [14:06] |
| .............................................................................. (idle for 6h29mn) | ||
| *** | markus_ changes his alias to mrec | [20:35] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
