[vdr] VDR 2.0
Hi. VDR 1.x was MPEG2-only and recorded in MPEG-PES. Now that it can do MPEG4 AVC/AAC, and records in MPEG-TS, isn't it time to rename it 2.0 after 1.7.5? /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] power consumption, powertop and wakups per second with a af9015 device
Just to complete the picture, here's the powertop output while recording. Don't start cheering about less wakeups per second (1300 vs 2700). There's less wakups per second as the system doesn't get into idle mode as often, in the first place. -henrik PowerTOP version 1.10 (C) 2007 Intel Corporation CnAvg residency P-states (frequencies) C0 (cpu running)(64.8%) 1500 Mhz 7.2% polling 0.0ms ( 0.0%) 563 Mhz 0.0% C1 halt 0.0ms ( 0.0%) 375 Mhz 7.2% C20.4ms (15.5%) 188 Mhz85.6% C30.2ms (19.6%) Wakeups-from-idle per second : 1317.2 interval: 10.0s no ACPI power usage estimate available Top causes for wakeups: 60.2% (4542.7) USB device 5-1 : DVB-T 2 (Afatech) 38.4% (2898.3) interrupt : uhci_hcd:usb1, ehci_hcd:usb5, HDA Intel 0.7% ( 52.9) vdr-kbd : futex_wait (hrtimer_wakeup) 0.2% ( 12.8) interrupt : rtc0 0.2% ( 12.4) interrupt : uhci_hcd:usb3, eth0 0.0% ( 3.4) vdr-kbd : hrtick_set (hrtick) 0.0% ( 3.2) mpd : hrtick_set (hrtick) 0.0% ( 3.1) interrupt : uhci_hcd:usb4, sata_sil24 0.0% ( 3.0) kernel core : sk_reset_timer (tcp_delack_timer) 0.0% ( 2.0) mpd : sk_reset_timer (tcp_write_timer) 0.0% ( 2.0) xfsaild : schedule_timeout (process_timeout) 0.0% ( 1.6) xfsbufd : schedule_timeout (process_timeout) 0.0% ( 1.1) vdr-kbd : schedule_timeout (process_timeout) 0.0% ( 1.1) vdr-kbd : blk_plug_device (blk_unplug_timeout) 0.0% ( 1.0) ifconfig : b44_open (b44_timer) 0.0% ( 1.0) klogd : ehci_work (ehci_watchdog) 0.0% ( 0.9)kdvb-ad-0-fe-0 : schedule_timeout (process_timeout) 0.0% ( 0.5) kernel core : schedule_delayed_work_on (delayed_work_timer_fn) 0.0% ( 0.3) kernel module : neigh_table_init_no_netlink (neigh_periodic_timer) 0.0% ( 0.2) chronyd : schedule_timeout (process_timeout) 0.0% ( 0.2) kernel core : inet_twsk_schedule (inet_twdr_hangman) 0.0% ( 0.2) runsvdir : schedule_timeout (process_timeout) 0.0% ( 0.2) init : schedule_timeout (process_timeout) 0.0% ( 0.2) kernel core : __netdev_watchdog_up (dev_watchdog) 0.0% ( 0.2) kernel core : neigh_table_init_no_netlink (neigh_periodic_timer) 0.0% ( 0.1) chronyd : do_adjtimex (sync_cmos_clock) 0.0% ( 0.1) xfssyncd : schedule_timeout (process_timeout) 0.0% ( 0.1) nmbd : schedule_timeout (process_timeout) 0.0% ( 0.1)screen : do_setitimer (it_real_fn) 0.0% ( 0.1) kernel core : neigh_add_timer (neigh_timer_handler) 0.0% ( 0.1) mpd : blk_plug_device (blk_unplug_timeout) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 2.0
Magnus Hörlin schrieb: Hi. VDR 1.x was MPEG2-only and recorded in MPEG-PES. Now that it can do MPEG4 AVC/AAC, and records in MPEG-TS, isn't it time to rename it 2.0 after 1.7.5? /Magnus H Brilliant Idea. That will boost the sales numbers to the limits :) SCNR Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 2.0
ROTFL Peter Evertz schrieb: Magnus Hörlin schrieb: Hi. VDR 1.x was MPEG2-only and recorded in MPEG-PES. Now that it can do MPEG4 AVC/AAC, and records in MPEG-TS, isn't it time to rename it 2.0 after 1.7.5? /Magnus H Brilliant Idea. That will boost the sales numbers to the limits :) SCNR Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-iptv-0.2.5
Hi My issues. May be I not right, but 1. Have: use section filtering - yes, disable filters - 0. Have a iptv channel in channel.conf, but absent and not streaming now. Switch channels: work channnel - absent channel - work channel. And vdr hangs, almost always If set use section filtering - no, all works. If set use section filtering - yes, disable filters - 1, PAT, all works too. 2. pat.c use Channels.GetByServiceID. Channels.GetByServiceID use ISTRANSPONDER(). #define ISTRANSPONDER(f1, f2) (abs((f1) - (f2)) 4) We must use frequencies differ 4 in iptv channels. TV1;IPTV:1:IPTV|S1P0|UDP|127.0.0.1|1234:P:0:512:650:2321:0:1:0:0:0 - third parametr. Never use: TV1;IPTV:1:IPTV|S1P0.. TV1;IPTV:2:IPTV|S1P0.. TV1;IPTV:3:IPTV|S1P0.. need use (example): TV1;IPTV:10:IPTV|S1P0.. TV1;IPTV:20:IPTV|S1P0.. TV1;IPTV:30:IPTV|S1P0.. Otherwise ISTRANSPONDER() not works correct... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] power consumption, powertop and wakups per second with a af9015 device
Hei Antti,
On Mon, Mar 16, 2009 at 02:19:30PM +0200, Antti Palosaari wrote:
Heinrich Langos wrote:
That is with dvb_usb_af9015 loaded but with remote=0 module parameter
to disable the remote control input that aparently is done by polling.
remote=0 does not disable polling, it is for selecting correct remote.
Well, setting remote=0 does have an effect (af9015.c):
if (val == AF9015_IR_MODE_DISABLED || val == 0x04) {
af9015_properties[i].rc_key_map = NULL;
af9015_properties[i].rc_key_map_size = 0;
While every other (valid) value for remote assigns a key map at that point
and further sets the af9015_config.ir_table. I guess thats has consequences
so that even if polling occurrs, it doesn't cause a whole lot of other
actions.
You can disable polling by setting proper module param for module dvb-usb.
Where proper would be? :-)
(With remote=2 it goes up by about 50 wakeups per second. OK, AFAIK
USB input devices need to be polled. No way around it. But does it have
to be at 20ms intervals?)
hmm, It should be 150ms according to the code. No idea why it generates
50 wakeups.
My guess would be that each polling action generates several USB packets
which in turn cause several wakeups...
I have no idea why.
Does your vdr let your machine sleep nicely?
Cheers
-henrik
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 2.0
On Mon, Mar 16, 2009 at 6:05 AM, Peter Evertz l...@pec.homeip.net wrote: Magnus Hörlin schrieb: Hi. VDR 1.x was MPEG2-only and recorded in MPEG-PES. Now that it can do MPEG4 AVC/AAC, and records in MPEG-TS, isn't it time to rename it 2.0 after 1.7.5? /Magnus H Brilliant Idea. That will boost the sales numbers to the limits :) lol! One of the best posts I've seen in a while! ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-iptv-0.2.5
On Mon, 16 Mar 2009, ua0lnj wrote: 1. Have: use section filtering - yes, disable filters - 0. Have a iptv channel in channel.conf, but absent and not streaming now. Switch channels: work channnel - absent channel - work channel. And vdr hangs, almost always Could you attach the gdb to the vdr process and check where does it hang exactly? If set use section filtering - no, all works. If set use section filtering - yes, disable filters - 1, PAT, all works too. So, it's somehow related to cPatFilter. As the pid updating works nicely on my setup, this might be related to video stream data itself... 2. pat.c use Channels.GetByServiceID. Channels.GetByServiceID use ISTRANSPONDER(). #define ISTRANSPONDER(f1, f2) (abs((f1) - (f2)) 4) We must use frequencies differ 4 in iptv channels. TV1;IPTV:1:IPTV|S1P0|UDP|127.0.0.1|1234:P:0:512:650:2321:0:1:0:0:0 - third parametr. Never use: TV1;IPTV:1:IPTV|S1P0.. need use (example): TV1;IPTV:10:IPTV|S1P0.. Otherwise ISTRANSPONDER() not works correct... Did I understood you correctly: if you're setting the channel frequency to 10 instead of 1, your VDR won't hang anymore with section filtering (including PAT) enabled? Why would (abs(1-1)4) be different than abs(10-10)4? Anyway, you could trace the values given to ISTRANSPONDER() macro and see if that gives any hint about the problem. PS. You can also send bug reports and questions directly to me without polluting the mailing list. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] power consumption, powertop and wakups per second with a af9015 device
On Mon, Mar 16, 2009 at 05:23:53PM +0200, Antti Palosaari wrote:
Heinrich Langos wrote:
On Mon, Mar 16, 2009 at 03:07:21PM +0100, Heinrich Langos wrote:
On Mon, Mar 16, 2009 at 02:19:30PM +0200, Antti Palosaari wrote:
remote=0 does not disable polling, it is for selecting correct remote.
Well, setting remote=0 does have an effect (af9015.c):
if (val == AF9015_IR_MODE_DISABLED || val == 0x04) {
af9015_properties[i].rc_key_map = NULL;
af9015_properties[i].rc_key_map_size = 0;
val is read from eeprom, there is byte in eeprom which tells whether
device have remote or not. If eeprom says no remote then polling is
disabled.
If you look more carefully there is if-else condition which goes:
if (eeprom remote disabled)
* disable remote
else if (module param remote defined)
* load ir-table defined as module param
else
* load ir-table according to USB-ID
You are right. Sorry I didn't read that carefully enough.
I am not sure what happens if device have remote but ir-table is not
selected by if-else. Probably .rc_key_map_size leaves to 0 and remote
polling is disabled.
Thats exactly what happens. Though, I didn't see a place where
af9015_properties[i]rc_key_map is initalized. Maybe a sanity check
for the remote module parameter should be added? Telling the user that
he uses an invalid value could help new users.
Anyhow, this problem is not af9015 specified. Most dvb-usb -drivers have
just similar implementation. rc-polling is provided by dvb-usb-core.
Right again. Sorry to bother you.
Anyway .. the main problem remains.
Is there a tool that would only do some minimal actions on a dvb
device?
Like power_on? femon for example reads device status. zap, scan...
Yeap. Thank you for that list. I'll take a look at those and see what I can
find out.
Cheers and thank you very much for your help!
-henrik
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
