Re: [linux-dvb] Please help: Looking for a solidly supported DVB-T USB stick
Stephen Williams wrote: > Surely this can't be too much to ask? I'm looking for a DVB-T USB > stick which I can buy now and is solidly supported, that's all. > > Previously i've picked up a couple of MSI Digivox II sticks that when > delivered turned out to be unsupported MSI Digivox II V2.0 sticks, so > it's no longer safe to order those. Then I picked up a couple of MSI > Mega Sky 580 sticks (the x5581 version) which appear to be incapable > of receiving a decent signal under windows or linux (note that I > haven't had signal problems with 4 previous DVB-T receivers). > > So i'm now hoping for "third time lucky". Any suggestions of supported > devices that are known to work without issues would be greatly > appreciated. > > I've checked the wiki for information but it all seems to be completed > out of date. > I'm beginning to believe that from a tuning standpoint tinless tuners can't even remotely compare to tin-canned tuners (I tried quite a lot), let alone that they tend to overheat in short time and to perform even worse when heat rises. Maybe usb sticks are not the best choice if you want a stable reception, or maybe I simply stumbled on the crap of the crop (as usual) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Hi, As announced I've built a revised tarball plus a Debian package of the current dvb-apps repository, implying your patchset (i. e. human readable characters as a switch for szap, tzap and czap. Unfortunately both packages were rejected without giving reason by the list moderator of [EMAIL PROTECTED] I still want to share that work. As soon as my project will be ready I will be going to host stuff like that on my own project page at sourceforge. If someone needs one or both of the packages please drop me a short note. Uwe ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
On Sun, Jul 22, 2007, Uwe Bugla wrote: > > As announced I've built a revised tarball plus a Debian package of the > current > dvb-apps repository, implying your patchset (i. e. human readable characters > as a switch for szap, tzap and czap. > > Unfortunately both packages were rejected without giving reason by the list > moderator of [EMAIL PROTECTED] If you look at the reject messages, they should say: Reason: Message body is too big: 404226 bytes with a limit of 60 KB and Reason: Message body is too big: 517891 bytes with a limit of 60 KB The limit is there to protect people who don't have broadband connectivity, and to protect the list server (with ~2000 list subscribers, these two mails would have caused ~1.8 GByte of traffic). Johannes ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Am Sonntag, 22. Juli 2007 12:41:56 schrieb Johannes Stezenbach: > On Sun, Jul 22, 2007, Uwe Bugla wrote: > > As announced I've built a revised tarball plus a Debian package of the > > current dvb-apps repository, implying your patchset (i. e. human readable > > characters as a switch for szap, tzap and czap. > > > > Unfortunately both packages were rejected without giving reason by the > > list moderator of [EMAIL PROTECTED] > > If you look at the reject messages, they should say: > > Reason: Message body is too big: 404226 bytes with a limit of 60 KB > and > Reason: Message body is too big: 517891 bytes with a limit of 60 KB > > The limit is there to protect people who don't have broadband > connectivity, and to protect the list server (with ~2000 list > subscribers, these two mails would have caused ~1.8 GByte of traffic). > > > Johannes > Sounds logical. But the main reason you unfortunately forgot to mention: The limit is there to protect the "highly motivated illustrious" linuxtv gatekeepers from doing additional good work in order to share good efforts all around the world. I still got my own experiences and views on the difference between what real sophisticated maintainership means in practice @linuxtv.org in comparison to the rest of the world-wide linux community. In fact there is a big difference. For example, if I read comments like "you should first ask whether someone intends to pick it up (by Christoph Pfister in this specific example) the knife in my pocket opens. A real sophisticated maintainer picks up such efforts like P. van Gaans patch set and merges them without making any noise. Above that, the filter timeout problem in connection with "scan" still remains unsolved (wasn't it you, Johannes, who once wrote the scan utility?). Why is the scan result still such a drag? Why are the scan results so unreliable? Why are there channels missing in the final result? Is it a driver issue or an application issue? And who can help? Who has got the clue to fix that? And why does this problem not appear within kaffeine's channel scan? I'm not expecting any answer or fix for that problem - I can help myself. But I would like to know whether I am the only one to have that problem with the scan utility. Uwe > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
I propose we setup #linuxtv-without-jews on feenode and coordinate our efforts to take over those fools who run the real LinuxTV scam. -tc On 7/22/07, Uwe Bugla <[EMAIL PROTECTED]> wrote: > Am Sonntag, 22. Juli 2007 12:41:56 schrieb Johannes Stezenbach: > > On Sun, Jul 22, 2007, Uwe Bugla wrote: > > > As announced I've built a revised tarball plus a Debian package of the > > > current dvb-apps repository, implying your patchset (i. e. human readable > > > characters as a switch for szap, tzap and czap. > > > > > > Unfortunately both packages were rejected without giving reason by the > > > list moderator of [EMAIL PROTECTED] > > > > If you look at the reject messages, they should say: > > > > Reason: Message body is too big: 404226 bytes with a limit of 60 KB > > and > > Reason: Message body is too big: 517891 bytes with a limit of 60 KB > > > > The limit is there to protect people who don't have broadband > > connectivity, and to protect the list server (with ~2000 list > > subscribers, these two mails would have caused ~1.8 GByte of traffic). > > > > > > Johannes > > > > Sounds logical. But the main reason you unfortunately forgot to mention: > > The limit is there to protect the "highly motivated illustrious" linuxtv > gatekeepers from doing additional good work in order to share good efforts > all around the world. > > I still got my own experiences and views on the difference between what real > sophisticated maintainership means in practice @linuxtv.org in comparison to > the rest of the world-wide linux community. In fact there is a big > difference. > > For example, if I read comments like "you should first ask whether someone > intends to pick it up (by Christoph Pfister in this specific example) the > knife in my pocket opens. > A real sophisticated maintainer picks up such efforts like P. van Gaans patch > set and merges them without making any noise. > > Above that, the filter timeout problem in connection with "scan" still remains > unsolved (wasn't it you, Johannes, who once wrote the scan utility?). > > Why is the scan result still such a drag? Why are the scan results so > unreliable? Why are there channels missing in the final result? > Is it a driver issue or an application issue? > And who can help? Who has got the clue to fix that? > And why does this problem not appear within kaffeine's channel scan? > > I'm not expecting any answer or fix for that problem - I can help myself. > But I would like to know whether I am the only one to have that problem with > the scan utility. > > Uwe > > > ___ > > linux-dvb mailing list > > linux-dvb@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Am Sonntag, 22. Juli 2007 13:44:44 schrieb timecop: > I propose we setup #linuxtv-without-jews on feenode and coordinate our > efforts to take over those fools who run the real LinuxTV scam. > > -tc Hello tc, could you please stay off from here with such a no-brain antisemitistic verbal crap? Thanks Uwe > > On 7/22/07, Uwe Bugla <[EMAIL PROTECTED]> wrote: > > Am Sonntag, 22. Juli 2007 12:41:56 schrieb Johannes Stezenbach: > > > On Sun, Jul 22, 2007, Uwe Bugla wrote: > > > > As announced I've built a revised tarball plus a Debian package of > > > > the current dvb-apps repository, implying your patchset (i. e. human > > > > readable characters as a switch for szap, tzap and czap. > > > > > > > > Unfortunately both packages were rejected without giving reason by > > > > the list moderator of [EMAIL PROTECTED] > > > > > > If you look at the reject messages, they should say: > > > > > > Reason: Message body is too big: 404226 bytes with a limit of 60 KB > > > and > > > Reason: Message body is too big: 517891 bytes with a limit of 60 KB > > > > > > The limit is there to protect people who don't have broadband > > > connectivity, and to protect the list server (with ~2000 list > > > subscribers, these two mails would have caused ~1.8 GByte of traffic). > > > > > > > > > Johannes > > > > Sounds logical. But the main reason you unfortunately forgot to mention: > > > > The limit is there to protect the "highly motivated illustrious" linuxtv > > gatekeepers from doing additional good work in order to share good > > efforts all around the world. > > > > I still got my own experiences and views on the difference between what > > real sophisticated maintainership means in practice @linuxtv.org in > > comparison to the rest of the world-wide linux community. In fact there > > is a big difference. > > > > For example, if I read comments like "you should first ask whether > > someone intends to pick it up (by Christoph Pfister in this specific > > example) the knife in my pocket opens. > > A real sophisticated maintainer picks up such efforts like P. van Gaans > > patch set and merges them without making any noise. > > > > Above that, the filter timeout problem in connection with "scan" still > > remains unsolved (wasn't it you, Johannes, who once wrote the scan > > utility?). > > > > Why is the scan result still such a drag? Why are the scan results so > > unreliable? Why are there channels missing in the final result? > > Is it a driver issue or an application issue? > > And who can help? Who has got the clue to fix that? > > And why does this problem not appear within kaffeine's channel scan? > > > > I'm not expecting any answer or fix for that problem - I can help myself. > > But I would like to know whether I am the only one to have that problem > > with the scan utility. > > > > Uwe > > > > > ___ > > > linux-dvb mailing list > > > linux-dvb@linuxtv.org > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > ___ > > linux-dvb mailing list > > linux-dvb@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please help: Looking for a solidly supported DVB-T USB stick
Stephen Williams wrote: > On 7/22/07, timecop <[EMAIL PROTECTED]> wrote: >> Believe it or not, I don't think any of them are "solidly supported". >> >> USB bridge part should be down nicely, but since all the tuner / demod >> drivers are reverse engineered garbage (or even if they have docs, you >> got amateurs writing code), and as result don't work as good as >> expected... > > Thanks for your default troll response. > > Just because the code is reverse engineered or written by amateurs > doesn't mean that it can't work solidly. Certainly my old Nova-T PCI > card worked flawlessly but now i've moved to a mac mini so there's no > PCI. [ sorry for the rant, i'm writing to everyone excpet timecop ] as you already wrote, it's trolling, so you don't need to justify.. we all bery well know how free software communities run and strive to give the best not only as a simple volunteer effort but also for straight economical reasons ( reliability, control, efficiency, standardization etc..). > > Does anyone have comments on the Nova-TD / Pinnacle Diversity (i.e. > dual DVB-T tuner) support? i do own a pinnacle diversity dvb-t usb dual tuner card and i used it with an additional patch: http://www.chez.com/treza/mt2266.htm http://www.linuxtv.org/pipermail/linux-dvb/2007-February/016166.html it works reliably as a dual tuner card. the diversity feature is not working (for dual tuner operations, you need both the antennae input connected..) bye andrea venturi ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
pot calling the kettle black anyone? On 7/22/07, Uwe Bugla <[EMAIL PROTECTED]> wrote: > Am Sonntag, 22. Juli 2007 13:44:44 schrieb timecop: > > I propose we setup #linuxtv-without-jews on feenode and coordinate our > > efforts to take over those fools who run the real LinuxTV scam. > > > > -tc > > Hello tc, > could you please stay off from here with such a no-brain antisemitistic verbal > crap? > > Thanks > > Uwe > > > > > On 7/22/07, Uwe Bugla <[EMAIL PROTECTED]> wrote: > > > Am Sonntag, 22. Juli 2007 12:41:56 schrieb Johannes Stezenbach: > > > > On Sun, Jul 22, 2007, Uwe Bugla wrote: > > > > > As announced I've built a revised tarball plus a Debian package of > > > > > the current dvb-apps repository, implying your patchset (i. e. human > > > > > readable characters as a switch for szap, tzap and czap. > > > > > > > > > > Unfortunately both packages were rejected without giving reason by > > > > > the list moderator of [EMAIL PROTECTED] > > > > > > > > If you look at the reject messages, they should say: > > > > > > > > Reason: Message body is too big: 404226 bytes with a limit of 60 KB > > > > and > > > > Reason: Message body is too big: 517891 bytes with a limit of 60 KB > > > > > > > > The limit is there to protect people who don't have broadband > > > > connectivity, and to protect the list server (with ~2000 list > > > > subscribers, these two mails would have caused ~1.8 GByte of traffic). > > > > > > > > > > > > Johannes > > > > > > Sounds logical. But the main reason you unfortunately forgot to mention: > > > > > > The limit is there to protect the "highly motivated illustrious" linuxtv > > > gatekeepers from doing additional good work in order to share good > > > efforts all around the world. > > > > > > I still got my own experiences and views on the difference between what > > > real sophisticated maintainership means in practice @linuxtv.org in > > > comparison to the rest of the world-wide linux community. In fact there > > > is a big difference. > > > > > > For example, if I read comments like "you should first ask whether > > > someone intends to pick it up (by Christoph Pfister in this specific > > > example) the knife in my pocket opens. > > > A real sophisticated maintainer picks up such efforts like P. van Gaans > > > patch set and merges them without making any noise. > > > > > > Above that, the filter timeout problem in connection with "scan" still > > > remains unsolved (wasn't it you, Johannes, who once wrote the scan > > > utility?). > > > > > > Why is the scan result still such a drag? Why are the scan results so > > > unreliable? Why are there channels missing in the final result? > > > Is it a driver issue or an application issue? > > > And who can help? Who has got the clue to fix that? > > > And why does this problem not appear within kaffeine's channel scan? > > > > > > I'm not expecting any answer or fix for that problem - I can help myself. > > > But I would like to know whether I am the only one to have that problem > > > with the scan utility. > > > > > > Uwe > > > > > > > ___ > > > > linux-dvb mailing list > > > > linux-dvb@linuxtv.org > > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > > > ___ > > > linux-dvb mailing list > > > linux-dvb@linuxtv.org > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > ___ > > linux-dvb mailing list > > linux-dvb@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] better choice for PCI DVB-T card
All right, I got only one response so far, privately. So, allow me a bit of a "bump". On top of that, I'd really like a dual-tuners solution. I have only 2 PCI slots in my machine, and one of them will be for a DVB-S card. timecop, no, really, no MCE for me, for my own education I just tried Vista's. 1 GB or RAM if not enough for that thing? What a shocker ! And it is as stable as ever...not! Nico http://www.youplala.net/linux/home-theater-pc/ On Fri, 2007-07-20 at 11:04 +0100, Nicolas Will wrote: > Hi all, > > I am still seting up that MythTV box. So far, it works great with my > Freecom DVB-T USB stick. > > Nevertheless, I am listening to the warning that those sticks are not > too good in the medium/long term, and I am looking at PCI cards. > > I also want to get a proper remote system with such a card. > > The local store in Aberdeen, Scotland has a few choices. > > I have reviewed the Wiki,and followed the mailing list, but still would > like advice from the people in the know of the latest driver progress. > > * Hauppauge WinTV-HVR 1100 - Looks like completely supported > * Analog - Don't need it > * DVB-T > * FM Radio - Does it work? > * Remote > * Hauppauge WinTV-HVR 1300 > * Analog - Don't need it > * DVB-T > * MPEG-2 encoder for Analog - Don't need it > * FM Radio - Does it work? > * Remote > * Hauppauge WinTV Nova-T 500 > * Dual DVB-T tuners > * Remote > * Pinnacle PCTV hybrid Pro - Not in wiki, Pinnacle support looks > sketchy > * Analog - Don't need it > * DVB-T > * Remote > > I'm dropping the Pinnacle from my choices. > > The Hauppauge Nova T-500 would be interesting, but support looks bad, > and I probably shouldn't trust its USB nature, should I? Furthermore, > the remote is apparently not supported. Any progress/change onthis that > I missed? > > That leaves me with the Hauppauge HVR models. The 1100 is probably what > I need. > > I will welcome you experience, opinion, advice and corrections. > > Nico > > Note to Timecop: no MCE for me, thanks! > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] OHauppauge WinTV HVR-3000 or 4000
One more... Hauppauge WinTV HVR-4000 - DVB-S2 / DVB-S / DVB-T receiver / analogue TV / radio tuner / video input adapter - PCI - SECAM, PAL Hauppauge WinTV HVR-3000 - DVB-S / DVB-T receiver / analogue TV / radio tuner / video input adapter - PCI - SECAM, PAL What about these cards? Any support, I have not seen them in the wiki? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] BBC HD DVB-T lost
Hi, I can't find anymore BBC HD signal via DVB-T in London I used to have these settings BBC HD1:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:1502:1505:36932 but now this is what I get with tzap using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/andrea/.tzap/channels.conf' tuning to 55400 Hz video pid 0x05de, audio pid 0x05e1 status 01 | signal 0c79 | snr | ber 001f | unc | status 01 | signal 0cb3 | snr | ber 001f | unc | status 01 | signal 0ce5 | snr | ber 001f | unc | status 01 | signal 0ccb | snr | ber 001f | unc | status 01 | signal 0ccb | snr | ber 001f | unc | status 01 | signal 0d0c | snr | ber 001f | unc | status 01 | signal 0d2a | snr | ber 001f | unc | status 01 | signal 0d4a | snr | ber 001f | unc | I lost reception about 1 - 2 months ago. Can anybody receive BBC HD via DVB-T in London? Thanks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Le dimanche 22 juillet 2007 13:44, timecop a écrit : > I propose we setup #linuxtv-without-jews on feenode and coordinate our > efforts to take over those fools who run the real LinuxTV scam. > > -tc FYI, I've just forwarded this mail to www.licra.org -- Christophe Thommeret ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Am Sonntag, 22. Juli 2007 17:37:48 schrieb Christophe Thommeret: > Le dimanche 22 juillet 2007 13:44, timecop a écrit : > > I propose we setup #linuxtv-without-jews on feenode and coordinate our > > efforts to take over those fools who run the real LinuxTV scam. > > > > -tc > > FYI, I've just forwarded this mail to www.licra.org Salut Christophe, Forwarding the message of this timecop idiot to licra.org may be politically correct and consequent in a left or progressive point of view that I share with you. But IMHO you are just paying too much attention to that idiot. Timecop is not only stupid and dumb as dumb can be (According to Einstein dumbness is endless as you surely know), but moreover he is a good example that even blacks are not free from racism and antisemitism. I do not want to overestimate people like timecop, but Malcolm X is another sad example for that basic thesis. See, Christophe, if you spend a whole lot of life time for demonstrating against warfare and racism, and if you, like me, live 10 kilometers away from the Nato headquarter you can easily see what intellectual weight class of American folks the government hires to transform no brains into killer machines to be sent to Iraq and Afghanistan f. ex. The prototype of an American soldier is and was and always will be a no brain human being! So it's best to simply ignore people like timecop. If noone pays attention to people of his intellectual weight class he'll piss off himself! And I also think he is a shame for the international gays movement too. Au revoir On se verra Uwe ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] OHauppauge WinTV HVR-3000 or 4000
Nicolas Will wrote: > One more... > > > Hauppauge WinTV HVR-4000 - DVB-S2 / DVB-S / DVB-T receiver / analogue > TV / radio tuner / video input adapter - PCI - SECAM, PAL > > Hauppauge WinTV HVR-3000 - DVB-S / DVB-T receiver / analogue TV / radio > tuner / video input adapter - PCI - SECAM, PAL > > What about these cards? > > Any support, I have not seen them in the wiki? > The HVR-3000 is "supported" by a branch created by Steven Toth. It's not seen any updates in a while, and currently (as far as I know) doesn't compile with kernels after 2.6.18. It's working ok for me here though. I think the reason for no updates / lack of inclusion in mainline dvb is that he is waiting for some sort of multi-protocol code to be implemented into the mainline dvb code. I believe the HVR-4000 has some support - there were a few mails about it some time ago on this list - again I believe Steven Toth has a separate tree that supports it, but I have no idea of status of that. Robert. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [Fwd: Re: OHauppauge WinTV HVR-3000 or 4000]
Original Message Subject: Re: [linux-dvb] OHauppauge WinTV HVR-3000 or 4000 Date: Sun, 22 Jul 2007 20:25:51 +0200 From: Uwe Schmeling <[EMAIL PROTECTED]> To: Robert <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Robert wrote: > Nicolas Will wrote: > >> One more... >> >> >> Hauppauge WinTV HVR-4000 - DVB-S2 / DVB-S / DVB-T receiver / analogue >> TV / radio tuner / video input adapter - PCI - SECAM, PAL >> >> Hauppauge WinTV HVR-3000 - DVB-S / DVB-T receiver / analogue TV / radio >> tuner / video input adapter - PCI - SECAM, PAL >> >> What about these cards? >> >> Any support, I have not seen them in the wiki? >> >> > > The HVR-3000 is "supported" by a branch created by Steven Toth. It's > not seen any updates in a while, and currently (as far as I know) > doesn't compile with kernels after 2.6.18. It's working ok for me here > though. I think the reason for no updates / lack of inclusion in > mainline dvb is that he is waiting for some sort of multi-protocol code > to be implemented into the mainline dvb code. > > I believe the HVR-4000 has some support - there were a few mails about > it some time ago on this list - again I believe Steven Toth has a > separate tree that supports it, but I have no idea of status of that. > > Robert. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Hi Robert, I have a HVR4000 running stable with a 2.6.21 kernel patched with Stevens tree. It is running stable since weeks (with DVB-S) and I would like to have it in the standard soon, even if the DVB-T part isn't supported currently. The integration into newer kernels requires some additional patches and I will continue testing as soon as it is in the standard. regards Uwe ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] bus control
Hi all, On one of the devices that i am working upon, it has a bus control entity. ie The device looks like this The device consists of 1) a BUS Interface Unit 2) on this bus Interface unit (BIU) there is one single physical I2C bus 3) a built in MASTER demodulator The I2C bus on the device is _not_ directly connected to any peripherals such as demods and or tuners. The bus goes to a control unit where the bus is split into 2 based on a control word sent to the Bus Control Unit (BCU) The split out bus goes out like this 1) goes to the MASTER tuner for the built in demodulator 2) goes to a SLAVE demodulator, which has just one switchable I2C output for the tuner ie , the configuration looks like 2, 2 way switches cascaded together, when the MASTER and SLAVE demodulators are cascaded. Looking at the device and thinking a lot, i don't see how the control can fit in as a part of the frontend at all, as the it has nothing to do with the frontend, but just the BIU. Some thought that i have, at present go like this * register independant virtual buses for each device, on device access, the relevant control word is appended to the BIU device register. * have one bus alone, but add a control for the bus such that the control can be initiated from some place, but as i explained, this control is not on the frontend/demodulator but on the Host controller. I would like to hear comments people have on this, or better ideas if any. Thanks, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap, czap and szap - new tarball and Debian package
Uwe Bugla wrote: > Am Sonntag, 22. Juli 2007 13:44:44 schrieb timecop: > >>I propose we setup #linuxtv-without-jews on feenode and coordinate our >>efforts to take over those fools who run the real LinuxTV scam. >> >>-tc > > > Hello tc, > could you please stay off from here with such a no-brain antisemitistic > verbal > crap? > > Thanks > > Uwe generally I don't reply to Uwe's mails, but I have to say that tc's sentence is one of the most horrible thing I ever read in any mailing list. Those things can't be said neither seriously nor for kidding. Shame! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
Am Sonntag, 22. Juli 2007 22:07:32 schrieb Manu Abraham: > Hi all, > > On one of the devices that i am working upon, it has a bus control entity. > ie > > The device looks like this > > The device consists of > > 1) a BUS Interface Unit > 2) on this bus Interface unit (BIU) there is one single physical I2C bus > 3) a built in MASTER demodulator > > > The I2C bus on the device is _not_ directly connected to any > peripherals such as demods and or tuners. > > The bus goes to a control unit where the bus is split into 2 based on > a control word sent to the Bus Control Unit (BCU) > > The split out bus goes out like this > > 1) goes to the MASTER tuner for the built in demodulator > 2) goes to a SLAVE demodulator, which has just one switchable I2C > output for the tuner > > ie , the configuration looks like 2, 2 way switches cascaded together, > when the MASTER and SLAVE demodulators are cascaded. > > Looking at the device and thinking a lot, i don't see how the control > can fit in as a part of the frontend at all, as the it has nothing to > do with the frontend, but just the BIU. > > Some thought that i have, at present go like this > > * register independant virtual buses for each device, on device > access, the relevant control word is appended to the BIU device > register. > > * have one bus alone, but add a control for the bus such that the > control can be initiated from some place, but as i explained, this > control is not on the frontend/demodulator but on the Host controller. > > I would like to hear comments people have on this, or better ideas if any. > > Thanks, > Manu > Manu. although you're a rather selfish and utmost egoist human being who has destroyed and turned down a lot of good people's efforts by your inside living proven selfishness and egoism: If you could formulate your request a bit less abstract and more filled up with some examples then there could be at least a small chance that you get some answer at all on your request. Anyway I got real sick of your attitudes and manners (i. e. no time windows, just empty promises never to be fulfilled and so on..). It feels real sucking up with you everytime one feels that you do not have any clue to solve problems that indeed are existing! If you still claim to be a core maintainer then please show people that you indeed provide the virtues of a real core maintainer. Otherwise stay away from claiming to be one! The basic virtues are: 1. reliability and 2. high communication level! And please stick to one basic rule or simply leave it and get outta here: You personally are measured by your positive results (i. e. producing well functionable and effective good drivers, no disfunctionable crap, whatever device it may be!) Regards Uwe P. S.: Above all my criticism on you personally I still share the basic thought with you that Mauro "the horse" Chehab is, regarding his real capabilities and his basic attitudes towards a common linuxtv project, just another "Apparatschnik" mismatch that absolutely noone needs! The basic rule of mismatch is: Every fish starts stinking from the head down to the tail, not and never vice versa!! And this goes for Mister Johannes Stezenbach too > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] BBC HD DVB-T lost
The trial ended on Freeview about a month ago. A sad loss :-( The trial is continuing on cable and satellite. Regards, Soyeb On Sun, 2007-07-22 at 15:37 +0100, Mario Rossi wrote: > Hi, > > I can't find anymore BBC HD signal via DVB-T in London > > I used to have these settings > > BBC > HD1:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:1502:1505:36932 > > but now this is what I get with tzap > > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > reading channels from file '/home/andrea/.tzap/channels.conf' > tuning to 55400 Hz > video pid 0x05de, audio pid 0x05e1 > status 01 | signal 0c79 | snr | ber 001f | unc | > status 01 | signal 0cb3 | snr | ber 001f | unc | > status 01 | signal 0ce5 | snr | ber 001f | unc | > status 01 | signal 0ccb | snr | ber 001f | unc | > status 01 | signal 0ccb | snr | ber 001f | unc | > status 01 | signal 0d0c | snr | ber 001f | unc | > status 01 | signal 0d2a | snr | ber 001f | unc | > status 01 | signal 0d4a | snr | ber 001f | unc | > > I lost reception about 1 - 2 months ago. > Can anybody receive BBC HD via DVB-T in London? > > Thanks > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
Hi Manu, Manu Abraham wrote: > * register independant virtual buses for each device, on device > access, the relevant control word is appended to the BIU device > register. this solution is easy to implement and does not require the frontend driver to know about its underlying bus. Just protect your master_xfer function with a mutex, grab it, configure the bus control unit, transfer the message and release the mutex before returning. Regards, Andreas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
On 7/23/07, Manu Abraham <[EMAIL PROTECTED]> wrote:
Hi all,
On one of the devices that i am working upon, it has a bus control entity. ie
The device looks like this
The device consists of
1) a BUS Interface Unit
2) on this bus Interface unit (BIU) there is one single physical I2C bus
3) a built in MASTER demodulator
The I2C bus on the device is _not_ directly connected to any
peripherals such as demods and or tuners.
The bus goes to a control unit where the bus is split into 2 based on
a control word sent to the Bus Control Unit (BCU)
The split out bus goes out like this
1) goes to the MASTER tuner for the built in demodulator
2) goes to a SLAVE demodulator, which has just one switchable I2C
output for the tuner
ie , the configuration looks like 2, 2 way switches cascaded together,
when the MASTER and SLAVE demodulators are cascaded.
Looking at the device and thinking a lot, i don't see how the control
can fit in as a part of the frontend at all, as the it has nothing to
do with the frontend, but just the BIU.
Some thought that i have, at present go like this
* register independant virtual buses for each device, on device
access, the relevant control word is appended to the BIU device
register.
* have one bus alone, but add a control for the bus such that the
control can be initiated from some place, but as i explained, this
control is not on the frontend/demodulator but on the Host controller.
Replying to my own mail: one second thoughts wondered whether i was
abstract a bit. Other than that when Christoph asked me on IRC on the
same, figured out that it was indeed a bit so.
The device what i mentioned has 2 demodulators and 2 tuners on one
physical I2C bus, which are accessed by selectively switching between
them, since the I2C addresses for the demods are the same. The only
separation being the switch.
So eventually, since words can be abstract, i prefer to depict it with
some code and comments alongwith. Attached is the code that would
control the tuner as well as the MASTER/SLAVE demods.
A note to Patrick: currently i am using the dvb-usb infrastructure. In
the current state dvb-usb uses one single I2C bus, if i were to use
virtual busses to utilize the MASTER/SLAVE combination, with a Control
Word Magic being sent to the device at the time of accessing the
virtual bus, eventually it goes down through the same physical bus.
The issue that i a facing i have depicted as comments in the code itself
Regards,
Manu
#define AF901x_GETFIELD(bitf, val) ((val >> AF901x_OFFST_##bitf) & \
((1 << AF901x_WIDTH_##bitf) - 1))
#define AF901x_SETFIELD(bitf, mask, val)(mask = (mask & (~(((1 << AF901x_WIDTH_##bitf) - 1)<< \
AF901x_OFFST_##bitf))) | (val << AF901x_OFFST_##bitf))
#define AF901x_BYPASS_HOST2TUNER 0xd607
#define AF901x_WIDTH_BYPASS_HOST2TUNER 1
#define AF901x_OFFST_BYPASS_HOST2TUNER 2
#define AF901x_I2CREG_SEL_TUNER 0xd417
#define AF901x_WIDTH_I2CREG_SEL_TUNER 1
#define AF901x_OFFST_I2CREG_SEL_TUNER 3
/**
* NOTE! What we do here is not a simple Tuner I2C Bus enable/disable !
* What's performed here is a 2 way switch kind of operation where
* the bus is switched between the demodulator and the tuner
*
* Of course we have a workaround (we have to), the enable bit can be
* used for enabling the tuner, which means the demodulator is disabled.
*
* A case where we get totally confused is when we have MASTER/SLAVE
* combinations
*
* The worst problem that we can have here: once we switch the
* tuner bypass ON and expecting an error and the transaction aborts,
* The driver expects the device to be communicating to the demodulator,
* but in reality we are talking to the tuner in fact.
*
* A workaround for this would be to cache the gate switched state
* into the device state structure, whereby a possible operation
* returned success state is used to switch the gate status back to the
* original position, such that normal communication can continue with
* the demodulator.
*
* But with all these workarounds don't we look ugly ? Any better ways
* of accomplishing this ?
*/
static int af901x_i2c_gate_ctrl(struct dvb_frontend *fe, int enable)
{
u8 reg;
if (slave) {
/**
* Additionally, we need to tell the BCU that we are
* talking to the SLAVE, How ?
*/
af901x_read_reg(state, AF901x_BYPASS_HOST2TUNER, ®);
if (enable)
reg = AF901x_SETFIELD(BYPASS_HOST2TUNER, reg, 1);
else
reg = AF901x_SETFIELD(BYPASS_HOST2TUNER, reg, 0);
/**
* Additionally, we need to tell the BCU that we are
* talking to the SLAVE, How ?
*/
af901x_write_reg(state, AF901x_BYPASS_HOST2TUNER, reg);
} else {
/**
* Additionally, we need to tell the BCU that we are
* talking to the MASTER, How ?
*/
af901x_read_reg(state, AF901x_I2CREG_SEL_TUNER, ®);
if (enable)
reg = AF901x_GETFIELD(I2CREG_SEL_TUNER, reg, 1);
else
reg = AF901x_GETFIELD(I2CREG_SEL_TUNER, reg, 0);
/**
* Additionally, we need to tell the BCU that we
Re: [linux-dvb] bus control
Am Montag, den 23.07.2007, 00:07 +0400 schrieb Manu Abraham: > Hi all, > > On one of the devices that i am working upon, it has a bus control entity. ie > > The device looks like this > > The device consists of > > 1) a BUS Interface Unit > 2) on this bus Interface unit (BIU) there is one single physical I2C bus > 3) a built in MASTER demodulator > > > The I2C bus on the device is _not_ directly connected to any > peripherals such as demods and or tuners. > > The bus goes to a control unit where the bus is split into 2 based on > a control word sent to the Bus Control Unit (BCU) > > The split out bus goes out like this > > 1) goes to the MASTER tuner for the built in demodulator > 2) goes to a SLAVE demodulator, which has just one switchable I2C > output for the tuner > > ie , the configuration looks like 2, 2 way switches cascaded together, > when the MASTER and SLAVE demodulators are cascaded. > > Looking at the device and thinking a lot, i don't see how the control > can fit in as a part of the frontend at all, as the it has nothing to > do with the frontend, but just the BIU. > > Some thought that i have, at present go like this > > * register independant virtual buses for each device, on device > access, the relevant control word is appended to the BIU device > register. > > * have one bus alone, but add a control for the bus such that the > control can be initiated from some place, but as i explained, this > control is not on the frontend/demodulator but on the Host controller. > > I would like to hear comments people have on this, or better ideas if any. > > Thanks, > Manu Hi Manu, best open discussion concept since long, hardware is forcing. Hopefully brings some others back and leads out of ideology. Best Regards, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
Hi Obi, On 7/23/07, Andreas Oberritter <[EMAIL PROTECTED]> wrote: > Hi Manu, > > Manu Abraham wrote: > > * register independant virtual buses for each device, on device > > access, the relevant control word is appended to the BIU device > > register. > > this solution is easy to implement and does not require the frontend > driver to know about its underlying bus. > > Just protect your master_xfer function with a mutex, grab it, configure > the bus control unit, transfer the message and release the mutex before > returning. Ah, thanks for the pointer. A state machine based on transaction locks would be the best way to go about it. Also it has the advantage that the frontend and bus can be loosely coupled as we do now. Thanks, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
Hello Herman, On 7/23/07, hermann pitton <[EMAIL PROTECTED]> wrote: > Am Montag, den 23.07.2007, 00:07 +0400 schrieb Manu Abraham: > > Hi Manu, > > best open discussion concept since long, hardware is forcing. > > Hopefully brings some others back and leads out of ideology. > When having a discussion, always try not to carry an OT discussion under the same topic. Not that i am saying this is a very serious discussion, but what happens is that in case of serious discussions, people float away from what is being discussed with OT stuff. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge Nova-T 500 USB disconnects.
What is the status of resolving the USB disconnects with the Nova-T 500? I find I can still easily trigger them just by flicking through channels in MythTV. This has stopped me from being able to put a PC I built to service as a media centre. I'm using Linux kernel 2.6.22 and I used mercurial to get the latest v4l-dvb drivers. I compared the dib*.[ch] source files from mercurial against the DVB drivers in the kernel sources. They are basically the same except the kernel sources removed the '#if 0' sections that won't get compiled anyway. I'm not using EIT with the card as I read this can increase the chances of triggering the USB disconnect. Is there any way to avoid the USB disconnects with this card? Is there some setting; or a custom patch to either USB or the DVB drivers to fix it? Any help on making this card stable is appreciated. -- Jim Barber DDI Health ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] bus control
Am Montag, den 23.07.2007, 04:24 +0400 schrieb Manu Abraham: > Hello Herman, > > On 7/23/07, hermann pitton <[EMAIL PROTECTED]> wrote: > > Am Montag, den 23.07.2007, 00:07 +0400 schrieb Manu Abraham: > > > > > Hi Manu, > > > > best open discussion concept since long, hardware is forcing. > > > > Hopefully brings some others back and leads out of ideology. > > > > When having a discussion, always try not to carry an OT discussion > under the same topic. Not that i am saying this is a very serious > discussion, but what happens is that in case of serious discussions, > people float away from what is being discussed with OT stuff. OK, I'll stay out and see how long you can hide the bridges you sit on with your frontends. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] OT nonsense, was Re: bus control
On 7/23/07, hermann pitton <[EMAIL PROTECTED]> wrote: > Am Montag, den 23.07.2007, 04:24 +0400 schrieb Manu Abraham: > > Hello Herman, > > > > On 7/23/07, hermann pitton <[EMAIL PROTECTED]> wrote: > > > Am Montag, den 23.07.2007, 00:07 +0400 schrieb Manu Abraham: > > > > > > > > Hi Manu, > > > > > > best open discussion concept since long, hardware is forcing. > > > > > > Hopefully brings some others back and leads out of ideology. > > > > > > > When having a discussion, always try not to carry an OT discussion > > under the same topic. Not that i am saying this is a very serious > > discussion, but what happens is that in case of serious discussions, > > people float away from what is being discussed with OT stuff. > > OK, I'll stay out and see how long you can hide the bridges you sit on > with your frontends. > Eh ? Head got too warm ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T 500 USB disconnects.
El Lunes, 23 de Julio de 2007, Jim Barber escribió:
> What is the status of resolving the USB disconnects with the Nova-T 500?
>
> I find I can still easily trigger them just by flicking through channels in
> MythTV. This has stopped me from being able to put a PC I built to service
> as a media centre.
>
> I'm using Linux kernel 2.6.22 and I used mercurial to get the latest
> v4l-dvb drivers. I compared the dib*.[ch] source files from mercurial
> against the DVB drivers in the kernel sources. They are basically the same
> except the kernel sources removed the '#if 0' sections that won't get
> compiled anyway.
>
> I'm not using EIT with the card as I read this can increase the chances of
> triggering the USB disconnect. Is there any way to avoid the USB
> disconnects with this card?
> Is there some setting; or a custom patch to either USB or the DVB drivers
> to fix it?
>
> Any help on making this card stable is appreciated.
>
> --
> Jim Barber
> DDI Health
>
I am using a dirty hack to try to avoid USB disconnects, and still don't have
a disconnect in three days, but I don't know if it solve the problem. I use
vdr. You can try it.
Jose Alberto
diff -r f96f68c4e5d9 linux/drivers/media/dvb/dvb-usb/dib0700_core.c
--- a/linux/drivers/media/dvb/dvb-usb/dib0700_core.c Thu Jul 19 18:06:54 2007 -0300
+++ b/linux/drivers/media/dvb/dvb-usb/dib0700_core.c Fri Jul 20 13:58:07 2007 +0200
@@ -238,6 +238,9 @@ int dib0700_streaming_ctrl(struct dvb_us
struct dib0700_state *st = adap->dev->priv;
u8 b[4];
+ if ((onoff != 2) && (onoff != 3))
+ return 0;
+
b[0] = REQUEST_ENABLE_VIDEO;
b[1] = 0x00;
b[2] = (0x01 << 4); /* Master mode */
@@ -245,7 +248,7 @@ int dib0700_streaming_ctrl(struct dvb_us
deb_info("modifying (%d) streaming state for %d\n", onoff, adap->id);
- if (onoff)
+ if (onoff == 2)
st->channel_state |= 1 << adap->id;
else
st->channel_state &= ~(1 << adap->id);
diff -r f96f68c4e5d9 linux/drivers/media/dvb/frontends/dib3000mc.c
--- a/linux/drivers/media/dvb/frontends/dib3000mc.c Thu Jul 19 18:06:54 2007 -0300
+++ b/linux/drivers/media/dvb/frontends/dib3000mc.c Sat Jul 21 14:30:51 2007 +0200
@@ -21,6 +21,7 @@
#include "dvb_frontend.h"
#include "dib3000mc.h"
+#include "dvb-usb.h"
static int debug;
module_param(debug, int, 0644);
@@ -316,6 +317,7 @@ static int dib3000mc_init(struct dvb_fro
{
struct dib3000mc_state *state = demod->demodulator_priv;
struct dibx000_agc_config *agc = state->cfg->agc;
+ struct dvb_usb_adapter *adap = demod->dvb->priv;
// Restart Configuration
dib3000mc_write_word(state, 1027, 0x8000);
@@ -429,12 +431,17 @@ static int dib3000mc_init(struct dvb_fro
/* close the i2c-gate */
dib3000mc_write_word(state, 769, (1 << 7) );
+ adap->props.streaming_ctrl(adap,2);
+
return 0;
}
static int dib3000mc_sleep(struct dvb_frontend *demod)
{
struct dib3000mc_state *state = demod->demodulator_priv;
+ struct dvb_usb_adapter *adap = demod->dvb->priv;
+
+ adap->props.streaming_ctrl(adap,3);
dib3000mc_write_word(state, 1031, 0x);
dib3000mc_write_word(state, 1032, 0x);
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] What is the problem with my mail?
>在2007-07-20，"David Woodhouse" <[EMAIL PROTECTED]> 写道： On Fri, >2007-07-20 > at 09:10 +0800, lwtbenben wrote: >> What is the problem with my mail, why is it so ugly. >> Can some guy help me? >See http://david.woodhou.se/email.html >In particular points 4, 5, 6, 7 and 8. Hi,David Thank you and I will follow the step. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge Nova-T 500 USB disconnects.
Jose Alberto Reguero wrote: > > I am using a dirty hack to try to avoid USB disconnects, and still don't > have > a disconnect in three days, but I don't know if it solve the problem. I use > vdr. You can try it. > > Jose Alberto Thanks Jose. That looks like quite a simple patch so I'll give it a go and see what happens. Out of interest, is this a patch that is a candidate for future merging pending some testing? (ie should I be providing some feedback on it?) Or is it truly just a "dirty hack" :) that will never see the light of day in the released sources? Regards, -- Jim Barber ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] My USB composite device.
Hi, everyone Dose Linux USB subsystem give any support about USB composite device? What should I do to drive my USB tv card which uses a composite USB device? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] My USB composite device.
Hi, Sorry for off topic, but please try do not use webmails to send mail to this list? The HTML encoded mails' format will corrupt the format while we are quoting your words. And your mail contains some annoying advertisement which may harm ths list. Thanks. Best regards, Lo Chun Chung (Chung) [EMAIL PROTECTED] HK. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of lwtbenben Sent: Monday, 23 July, 2007 9:24 AM To: linux-dvb Subject: [linux-dvb] My USB composite device. Hi, everyone Dose Linux USB subsystem give any support about USB composite device? What should I do to drive my USB tv card which uses a composite USB device? 劲 爆 150 万 同 时 在 线，众 人 追 捧 梦 幻 西 游 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] OT nonsense, was Re: bus control
> > > > OK, I'll stay out and see how long you can hide the bridges you sit on > > with your frontends. > > > > Eh ? Head got too warm ? 36.7 left and 36.6 right. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hauppauge Nexus-S (saa7146) on Feisty AMD64
I am attempting to rebuild a system with a hauppauge Nexus-s card under Ubuntu Feisty for AMD64 No matter what I do, I cannot get the system to load the card properly...or generate any errors. I have udev set to 'debug'. The only message in the logs is: [102.449709] saa7146: register extension 'dvb'. Running lsmod yields: dvb_ttpci 04 0 dvb_core 93872 1 dvb_ttpci saa7146_vv 54400 1 dvb_ttpci saa714621896 2 dvb_ttpci,saa7146_vv ttpci_eeprom3840 1 dvb_ttpci i2c_core 26496 5 i2c_ec,dvb_ttpci,ttpci_eeprom,nvidia,i2c_nforce2 I've also recompiled v4l-dvb and dvb-apps and manually created the device nodes...to no effect. Previously, this system was running well under dapper using the same card/configuration. My pcHDTV card loads without fanfare. Thoughts? -- "A man is defined by the questions that he asks; and the way he goes about finding the answers to those questions is the way he goes through life." ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
