Re: [vdr] power consumption, powertop and wakups per second with a af9015 device, vp7045, and various plugins
Antti Palosaari wrote: > Heinrich Langos wrote: >> Moikka Antti, >> >>> vp7045 does not have PID-filters. >>> I think difference comes from different USB-transfer settings. vp7045 >>> uses BULK packet size 4096 and af9015 uses BULK packet size 512 for >>> USB2.0 and BULK packet size 64 for USB1.1. Therefore af9015 sends 8 >>> times more packets than vp7045 (I guess). >>> >>> One thing more you can test - use USB1.1. To force USB1.1 remove USB2.0 >>> driver by rmmod ehci_hcd. After that plug af9015 stick and look from >>> logs it detects USB1.1 and uses PID-filters. af9015 driver now uses >>> smaller packet size for transfer that can change load (bigger?). > >> seems you are right. The transfer with PID filter in usb 1.1 causes >> about 30% load in contrast to 19% with usb 2.0 >> >> is there a way to increase the packet size for those bulk transfers? >> for usb 2.0? for 1.1? > > Actually AF9015 chip offers registers to configure packet size. But > those which are now used are default ones and rather many devices (other > than af9015) are using just same. That's why I am not sure if I want > change those to bigger ones. > > I will make test version that uses 4k packets for your tests. If it > resolves problem then we should consider for example adding module param > for setting desirable packet size. I will inform you when test version > is ready - It takes day or two. Unfortunately 512 seems to be biggest allowed packet size so I cannot increase it. Anyhow, there is other configurable parameter called packet count. I increased that from 348 to 512 but I doubt it does not have any effect. Feel free to test. If it does not change load then I think we cannot do more. Test tree: http://linuxtv.org/hg/~anttip/af9015_powertop/ regards Antti -- http://palosaari.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ADMIN] linuxtv.org is moving
Hi, linuxtv.org will move to a new server machine tomorrow. Expect some downtime during the move and please be patient. Everything on the old machine will be rsynced to the new machine right before the switch so nothing should get lost. Cheers, Johannes ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] noad for VDR 1.7.x
There are some discussions going on on the german VDR Portal: http://www.vdr-portal.de/board/thread.php?threadid=85297 2009/3/25 Peter : > Has there been any work to patch noad for new recording format in VDR > 1.7.4? > > 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] noad for VDR 1.7.x
Has there been any work to patch noad for new recording format in VDR 1.7.4? Peter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 & S2API - Channels not Available
For vdr-1.7.0+ You must change your channels.conf to reflect below: :12326:HM2O0S0:S110.0W :12457:VM2O0S0:S119.0W 8psk :12457:VC23M5O0S0:S110.0W: - Original Message - From: "LinuX Oholic" To: Sent: Wednesday, March 25, 2009 5:22 AM Subject: [vdr] VDR 1.7.0 & S2API - Channels not Available > > Hello vdr list > > I recently bought two Twinhan DVB-T receiver sticks: > > TwinhanDTV USB-Ter USB1.1 / Magic Box I & Magic Box II > > They both seem to work well in linux, but for some reason > I can only get a picture in stable c't vdr (1.6.0-2) and not in > my self compiled vdr 1.7.0. > > I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), > this one works fine on both vdr versions. > > Patchlevel on vdr 1.7.0 is: > > + h264-syncearly-framespersec-audioindexer-fielddetection-speedup > +vdr-1.7.0-s2api-07102008-h264-clean.patch > > From what I see in the 1.7.0 syslog I can make out a possible reason why > it doesn't work in there: > > vdr: [6675] [general.debug] capturing device 0 > vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) > vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) > vdr: [6675] device 1 provides: DVBS DSS > vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) > vdr: [6681] section handler thread started (pid=6675, tid=6681) > vdr: [6675] [general.info] captured 1 video device > > This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of > the > problem. I don't get this message in 1.6.0 at all. > > Is this related to the problem Morfsta had in [1] ? - it is the same QAM > 16 > modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). > > Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well > for > plugin compatibility reasons. > > [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html > > _ > http://redirect.gimas.net/?n=M0903xIMTicTacToe > Kostenlose Spannung? Spiel jetzt mit Freunden TIC TAC TOE in 3D! > ___ > 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 1.7.0 & S2API - Channels not Available
Hello vdr list I recently bought two Twinhan DVB-T receiver sticks: TwinhanDTV USB-Ter USB1.1 / Magic Box I & Magic Box II They both seem to work well in linux, but for some reason I can only get a picture in stable c't vdr (1.6.0-2) and not in my self compiled vdr 1.7.0. I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), this one works fine on both vdr versions. Patchlevel on vdr 1.7.0 is: + h264-syncearly-framespersec-audioindexer-fielddetection-speedup +vdr-1.7.0-s2api-07102008-h264-clean.patch >From what I see in the 1.7.0 syslog I can make out a possible reason why it doesn't work in there: vdr: [6675] [general.debug] capturing device 0 vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) vdr: [6675] device 1 provides: DVBS DSS vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) vdr: [6681] section handler thread started (pid=6675, tid=6681) vdr: [6675] [general.info] captured 1 video device This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of the problem. I don't get this message in 1.6.0 at all. Is this related to the problem Morfsta had in [1] ? - it is the same QAM 16 modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well for plugin compatibility reasons. [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html _ http://redirect.gimas.net/?n=M0903xIMTicTacToe Kostenlose Spannung? Spiel jetzt mit Freunden TIC TAC TOE in 3D! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 & S2API - Channels not Available
Hello vdr list I recently bought two Twinhan DVB-T receiver sticks: TwinhanDTV USB-Ter USB1.1 / Magic Box I & Magic Box II They both seem to work well in linux, but for some reason I can only get a picture in stable c't vdr (1.6.0-2) and not in my self compiled vdr 1.7.0. I use s2-liplianin drivers with another Twinhan DVB-S2 card (1041), this one works fine on both vdr versions. Patchlevel on vdr 1.7.0 is: + h264-syncearly-framespersec-audioindexer-fielddetection-speedup +vdr-1.7.0-s2api-07102008-h264-clean.patch >From what I see in the 1.7.0 syslog I can make out a possible reason why it doesn't work in there: vdr: [6675] [general.debug] capturing device 0 vdr: [6678] video directory scanner thread ended (pid=6675, tid=6678) vdr: [6677] video directory scanner thread ended (pid=6675, tid=6677) vdr: [6675] device 1 provides: DVBS DSS vdr: [6680] tuner on device 1 thread started (pid=6675, tid=6680) vdr: [6681] section handler thread started (pid=6675, tid=6681) vdr: [6675] [general.info] captured 1 video device This DVB-T stick is clearly *NOT* DVB-S capable - so this might be part of the problem. I don't get this message in 1.6.0 at all. Is this related to the problem Morfsta had in [1] ? - it is the same QAM 16 modulation I am trying to connect to - but mine is (QAM 16, 8K, 5/6, 1/4). Thanks in advance for any help. I'd like to stay with vdr 1.7.0 as well for plugin compatibility reasons. [1] http://www.linuxtv.org/pipermail/vdr/2009-February/019493.html _ http://redirect.gimas.net/?n=M0903xWLM2009 Neu: Messenger 2009! Hier kostenlos downloaden! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
