<div>Hi </div>
<div> Someone knew about dib7070p.<br><br> </div>
<div><span class="gmail_quote">On 8/19/07, <b class="gmail_sendername"><a href="mailto:linux-dvb-request@linuxtv.org">linux-dvb-request@linuxtv.org</a></b> <<a href="mailto:linux-dvb-request@linuxtv.org">linux-dvb-request@linuxtv.org
</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Send linux-dvb mailing list submissions to<br> <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org
</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb">http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb</a><br>or, via email, send a message with subject or body 'help' to
<br> <a href="mailto:linux-dvb-request@linuxtv.org">linux-dvb-request@linuxtv.org</a><br><br>You can reach the person managing the list at<br> <a href="mailto:linux-dvb-owner@linuxtv.org">linux-dvb-owner@linuxtv.org
</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of linux-dvb digest..."<br><br><br>Today's Topics:<br><br> 1. Re: [PATCH] add device node locking possibility to dvbcore
<br> (Andreas Oberritter)<br> 2. Re: [PATCH] add device node locking possibility to dvbcore<br> (Manu Abraham)<br> 3. Re: System load raises when budget_av is loaded (e9hack)<br> 4. Re: [PATCH] add device node locking possibility to dvbcore
<br> (Johannes Stezenbach)<br> 5. Re: [PATCH] add device node locking possibility to dvbcore<br> (Johannes Stezenbach)<br> 6. Re: [RFC] Hybrid tuner refactoring, phase 1 (Hans Verkuil)<br> 7. Re: [PATCH] saa7134: add DVB-T support for Avermedia Super
<br> 007 (hermann pitton)<br> 8. Re: [PATCH] saa7134: add DVB-T support for Avermedia Super<br> 007 (Michael Krufky)<br> 9. Re: [PATCH] saa7134: add DVB-T support for Avermedia Super<br> 007 (hermann pitton)
<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 19 Aug 2007 21:41:44 +0200<br>From: Andreas Oberritter <<a href="mailto:obi@linuxtv.org">obi@linuxtv.org
</a>><br>Subject: Re: [linux-dvb] [PATCH] add device node locking possibility<br> to dvbcore<br>To: Manu Abraham <<a href="mailto:abraham.manu@gmail.com">abraham.manu@gmail.com</a>><br>Cc: <a href="mailto:linux-dvb@linuxtv.org">
linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:46C89CF8.4010908@linuxtv.org">46C89CF8.4010908@linuxtv.org</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>Manu Abraham wrote:<br>> Oliver Endriss wrote:
<br>><br>>> Does anyone know, why dvb_shutdown_timeout was introduced initially?<br>>><br>><br>><br>> It was originally introduced looong time back by Obi.<br><br>Really? It's been five years since then, so I don't remember exactly
<br>where it came from. CVS indicates that it's Holger's code:<br><br><a href="http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.6.2.6&r2=1.6.2.7">http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.6.2.6&r2=1.6.2.7
</a><br><br>But the changelog lacks a reason for introducing it.<br><br>Regards,<br>Andreas<br><br><br><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 20 Aug 2007 00:18:32 +0400<br>From: Manu Abraham <
<a href="mailto:abraham.manu@gmail.com">abraham.manu@gmail.com</a>><br>Subject: Re: [linux-dvb] [PATCH] add device node locking possibility<br> to dvbcore<br>To: Andreas Oberritter <<a href="mailto:obi@linuxtv.org">
obi@linuxtv.org</a>><br>Cc: <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:46C8A598.10007@gmail.com">46C8A598.10007@gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1
<br><br>Andreas Oberritter wrote:<br>> Manu Abraham wrote:<br>>> Oliver Endriss wrote:<br>>><br>>>> Does anyone know, why dvb_shutdown_timeout was introduced initially?<br>>>><br>>><br>
>> It was originally introduced looong time back by Obi.<br>><br>> Really? It's been five years since then, so I don't remember exactly<br>> where it came from. CVS indicates that it's Holger's code:
<br>><br>> <a href="http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.6.2.6&r2=1.6.2.7">http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.6.2.6&r2=1.6.2.7</a><br>
><br>> But the changelog lacks a reason for introducing it.<br>><br><br>True.<br><br>What i meant to write got a bit inverted, i meant to write<br>dvb_shutdown_timeout=0 as in<br><a href="http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.36&r2=1.37">
http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/driver/dvb_frontend.c?r1=1.36&r2=1.37</a><br><br>Sorry for the confusion. (shouldn't probably write emails after looking<br>at code for long hours :-( )<br><br>Regards,
<br>Manu<br><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Sun, 19 Aug 2007 23:03:28 +0200<br>From: e9hack <<a href="mailto:e9hack@googlemail.com">e9hack@googlemail.com</a>><br>Subject: Re: [linux-dvb] System load raises when budget_av is loaded
<br>To: <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:46C8B020.6040008@gmail.com">46C8B020.6040008@gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br>
<br>Oliver Endriss schrieb:<br>> For full-featured cards it may take some time until the debi transfer<br>> has completed, because those cards use debi dma.<br><br>The max buffer size is 2k and the transfer rate is >12MB/s. The time for a transfer is lower than
<br>165usec.<br><br>><br>> I wonder<br>> - why the error bit gets set at all, and.<br>> - whether the debi status bits are updated before the transfer has<br>> been completed/stopped.<br><br>Depend on the spec, DEBI_E is set on a timeout or a debi error. DEBI_E is reset on the next upload.
<br>I don't know, what is going on.<br><br>- Hartmut<br><br><br><br><br>------------------------------<br><br>Message: 4<br>Date: Sun, 19 Aug 2007 23:10:02 +0200<br>From: Johannes Stezenbach <<a href="mailto:js@linuxtv.org">
js@linuxtv.org</a>><br>Subject: Re: [linux-dvb] [PATCH] add device node locking possibility<br> to dvbcore<br>To: <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:20070819211002.GA19421@linuxtv.org">
20070819211002.GA19421@linuxtv.org</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On Sun, Aug 19, 2007, Oliver Endriss wrote:<br>><br>> Does anyone know, why dvb_shutdown_timeout was introduced initially?
<br><br>That was a (IMHO stupid) hack by Holger with the purpose of speeding<br>up tuning with szap a little bit by avoiding the FE_INIT after<br>re-opening the frontend device. I.e. Holger's use-case was<br>to run szap, terminate if with ^C, re-run szap for different program.
<br>FE_INIT reintializes all demod registers so can take noticable time<br>if the i2c bus speed is slow.<br>IMHO dvb_shutdown_timeout never had any practical relevance.<br><br>BTW, Holger's preferred app for watching video was
<br><a href="http://linuxtv.org/hg/dvb-apps/file/tip/test/video.c">http://linuxtv.org/hg/dvb-apps/file/tip/test/video.c</a> :-)<br><br><br>Johannes<br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Sun, 19 Aug 2007 23:18:42 +0200
<br>From: Johannes Stezenbach <<a href="mailto:js@linuxtv.org">js@linuxtv.org</a>><br>Subject: Re: [linux-dvb] [PATCH] add device node locking possibility<br> to dvbcore<br>To: <a href="mailto:linux-dvb@linuxtv.org">
linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:20070819211842.GB19421@linuxtv.org">20070819211842.GB19421@linuxtv.org</a>><br>Content-Type: text/plain; charset=us-ascii<br><br>On Sun, Aug 19, 2007, Oliver Endriss wrote:
<br>><br>> Questions:<br>> - Why should dvb_shutdown_timeout==0 disable sleep mode?<br><br>The use case was to watch video without any software running.<br>Just program the hardware once and let it do it's job. Some
<br>people want that although I don't think it's really useful.<br>(Works for FF cards only, of course.)<br><br>> - Does it make any sense to have LNB power 'on' and the frontend in<br>> sleep mode?
<br><br>No.<br><br>> Imho these should be controlled by dvb_powerdown_on_sleep alone,<br>> for example:<br><br>Sounds good to me.<br><br><br>Johannes<br><br><br><br>------------------------------<br><br>Message: 6<br>
Date: Sun, 19 Aug 2007 23:38:13 +0200<br>From: Hans Verkuil <<a href="mailto:hverkuil@xs4all.nl">hverkuil@xs4all.nl</a>><br>Subject: Re: [linux-dvb] [RFC] Hybrid tuner refactoring, phase 1<br>To: <a href="mailto:video4linux-list@redhat.com">
video4linux-list@redhat.com</a><br>Cc: Linux DVB Mailing List <<a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a>>, Michael Krufky<br> <<a href="mailto:mkrufky@linuxtv.org">mkrufky@linuxtv.org
</a>><br>Message-ID: <<a href="mailto:200708192338.14034.hverkuil@xs4all.nl">200708192338.14034.hverkuil@xs4all.nl</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>On Sunday 19 August 2007 00:25:40 Michael Krufky wrote:
<br>> For the past few months, I've been working on refactoring the analog<br>> tuner.ko module, such that all hardware-specific code can be<br>> separated into dvb_frontend style tuner modules.<br>><br>> This allows for a single module to be used by both the v4l2 tuner
<br>> interface via the tuner.ko i2c_client driver, and directly by the dvb<br>> subsystem's tuning system.<br>><br>> This refactoring process has zero impact to the way that v4l and dvb<br>> functions.
<br>><br>> I have completed phase one of the refactoring process, and now it is<br>> ready for testing and review.<br>><br>> <a href="http://linuxtv.org/hg/~mkrufky/tuner-refactor-phase-1">http://linuxtv.org/hg/~mkrufky/tuner-refactor-phase-1
</a><br>><br>> A brief description of the individual changesets follows:<br>><br>> - tuner: kill i2c_client interface to tuner sub-drivers<br>><br>> This changeset removes the i2c_client interface between
tuner.ko and<br>> the tuner sub-drivers.<br>><br>> The i2c_client interface to tuner.ko, itself, remains the same as it<br>> has been -- this is only an internal change that affects the<br>> interaction between
tuner.ko and the hardware-specific code.<br>><br>> Some helper functions and macros were added in this changeset, in<br>> order to ease the conversion process, without causing headaches or<br>> breakage. (see
tuner-i2c.c) We can remove these extra structs and<br>> helper functions after the refactoring process is complete.<br>><br>> - hybrid tuner refactoring core changes, phase 1<br>><br>> This changeset contains the more interesting work, where tuner-core
<br>> is altered to support attachment of dvb_frontend style tuner modules.<br>> An additional method "set_analog_params" was added to struct<br>> dvb_tuner_ops, so as to avoid altering the DVB subsystem userspace
<br>> API headers. This change does not create any dependency of the DVB<br>> subsystem on V4L, nor does it create any dependency of the V4L<br>> subsystem on DVB.<br>><br>> - tda8290: convert from tuner sub-driver into dvb_frontend module
<br>> - mt20xx: convert from tuner sub-driver into dvb_frontend module<br>> - tea5761: convert from tuner sub-driver into dvb_frontend module<br>> - tea5767: convert from tuner sub-driver into dvb_frontend module
<br>> - tuner-simple: convert from tuner sub-driver into dvb_frontend<br>> module<br>><br>> These changesets handle the conversions of the individual tuner<br>> sub-drivers into dvb_frontend style tuner modules.
<br>><br>> - tuner: alter Makefile to produce separate modules<br>><br>> This changeset makes the changes to the build system, required for<br>> building the tuner sub-drivers as separate modules, and the ability
<br>> to deselect undesired tuner sub-drivers via Kconfig.<br>><br>> --------------------------------------------------<br>><br>> What comes next?<br>><br>> After phase 1 of hybrid tuner refactoring is merged into the master
<br>> branch, there is no change to the behavior of the drivers, apart from<br>> the fact that users will now have the ability to deselect undesired<br>> tuner sub-drivers via Kconfig.<br>><br>> I have the following changes planned for hybrid tuner refactoring,
<br>> phases 2, 3 and 4:<br>><br>> - analog if demodulator refactoring<br>><br>> In this step, an internal api for analog IF demods will be created,<br>> allowing us to refactor the tda9887 module, and also to handle
<br>> tda8290 separately from the tda8275 and tda8275a tuners.<br>><br>> - tda8290 refactoring<br>><br>> In addition to the analog if demodulator refactoring, duplicated code<br>> for the tda8275 and tda8275a tuners between
tda8290.ko and tda827x.ko<br>> shall be consolidated. In addition, support for the tda8295 and<br>> tda18271 devices will be added.<br>><br>> - tuner-simple refactoring<br>><br>> Tuner-simple will be cleaned up to take on more of an object-oriented
<br>> approach, and duplicated code for certain tuners present in both<br>> tuner-simple and dvb-pll shall be consolidated.<br>><br>> - miscellaneous work and additional cleanups<br>><br>> mt20xx shall be cleaned up to properly handle tuning requests from
<br>> the DVB subsystem, rather that going through tuner.ko -- this is a<br>> very small change, but I decided to wait on this until after phase 1<br>> is merged into master.<br>><br>> Support for new hybrid tuner hardware will now be _much_ easier to
<br>> develop and add into the v4l-dvb codebase.<br>><br>> --------------------------------------------------<br>><br>> I'd like to thank all of the people that have looked this over thus<br>> far, whom have given suggestions on how I can make this better and
<br>> easier to review.<br>><br>> If there are any other questions, comments or concerns, I would love<br>> to hear them. Please don't be shy -- feel free to let me know if you<br>> like or dislike this approach. I'd like to have this merged as soon
<br>> as possible, so that I may continue to work on the items mentioned<br>> about in the "What comes next?" section.<br>><br>> Now, it's time to go out and party! I will be able to respond to any
<br>> comments tomorrow afternoon.<br><br>Hi Mike,<br><br>I've reviewed your changes and it looks fine to me!<br><br>Acked-by: Hans Verkuil <<a href="mailto:hverkuil@xs4all.nl">hverkuil@xs4all.nl</a>><br><br>
Regards,<br><br> Hans<br><br><br><br>------------------------------<br><br>Message: 7<br>Date: Sun, 19 Aug 2007 23:39:21 +0200<br>From: hermann pitton <<a href="mailto:hermann-pitton@arcor.de">hermann-pitton@arcor.de
</a>><br>Subject: Re: [linux-dvb] [PATCH] saa7134: add DVB-T support for<br> Avermedia Super 007<br>To: <a href="mailto:bobbens@gmail.com">bobbens@gmail.com</a><br>Cc: <a href="mailto:video4linux-list@redhat.com">
video4linux-list@redhat.com</a>, <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:1187559561.3847.15.camel@pc08.localdom.local">1187559561.3847.15.camel@pc08.localdom.local
</a>><br>Content-Type: text/plain<br><br>Hi,<br><br>quick patches are always fine :)<br><br>Am Sonntag, den 19.08.2007, 19:56 +0200 schrieb <a href="mailto:bobbens@gmail.com">bobbens@gmail.com</a>:<br>> Hello,<br>>
<br>> After getting my card working I decided to hack up a patch to get<br>> autodetection working. With mkrufky's guidance I was able to make a<br>> patch he had few complaints of which I now include here.<br>
<br>This suggests somehow that Mike is fine with what you have so far.<br>I don't believe that.<br><br>We should not add new cards these days just by doing some code<br>duplication with the first working testing case on saa7134-dvb.
<br>(card=109)<br><br>Also this one should not be in the Philips Tigers eeprom detection IMHO.<br><br>We should know too, if it really has a LNA. The first guess working is<br>no equivalent for removing the tuner shielding. At least a test with
<br>config=0 should be done. Else we might stay in the dark, when more<br>assured hardware knowledge is needed in the future.<br><br>Mike please take over/comment.<br><br>Cheers,<br>Hermann<br><br>> This should get the DIGITAL part of the AVerMedia AVerTV DVB-T Super
<br>> 007, as noted in the patch ANALOG isn't working. I do not have windows<br>> installed and live in a pure linux environment (with bits of *BSD here<br>> and there). I'll try to see what I can do with a bit of testing, trying
<br>> some values for other cards (and hopefully not burning out mine). If<br>> anyone has windows and this card, please do it instead.<br>><br>> Haven't tested remote either, will get to that also soon.<br>
><br>> -bobbens<br><br><br><br><br><br>------------------------------<br><br>Message: 8<br>Date: Sun, 19 Aug 2007 17:53:16 -0400<br>From: Michael Krufky <<a href="mailto:mkrufky@linuxtv.org">mkrufky@linuxtv.org</a>
><br>Subject: Re: [linux-dvb] [PATCH] saa7134: add DVB-T support for<br> Avermedia Super 007<br>To: hermann pitton <<a href="mailto:hermann-pitton@arcor.de">hermann-pitton@arcor.de</a>><br>Cc: <a href="mailto:video4linux-list@redhat.com">
video4linux-list@redhat.com</a>, <a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:46C8BBCC.7010007@linuxtv.org">46C8BBCC.7010007@linuxtv.org</a>><br>Content-Type: text/plain; charset=ISO-8859-1
<br><br>hermann pitton wrote:<br>> Hi,<br>><br>> quick patches are always fine :)<br>><br>> Am Sonntag, den 19.08.2007, 19:56 +0200 schrieb <a href="mailto:bobbens@gmail.com">bobbens@gmail.com</a>:<br>>> Hello,
<br>>><br>>> After getting my card working I decided to hack up a patch to get<br>>> autodetection working. With mkrufky's guidance I was able to make a<br>>> patch he had few complaints of which I now include here.
<br>><br>> This suggests somehow that Mike is fine with what you have so far.<br>> I don't believe that.<br>><br>> We should not add new cards these days just by doing some code<br>> duplication with the first working testing case on saa7134-dvb.
<br>> (card=109)<br>><br>> Also this one should not be in the Philips Tigers eeprom detection IMHO.<br>><br>> We should know too, if it really has a LNA. The first guess working is<br>> no equivalent for removing the tuner shielding. At least a test with
<br>> config=0 should be done. Else we might stay in the dark, when more<br>> assured hardware knowledge is needed in the future.<br>><br>> Mike please take over/comment.<br><br><br>Hermann,<br><br>I showed him how to make a patch and suggested that he send it in to the mailing
<br>list for exactly this reason -- because I am not familiar with all the<br>intricacies of the various saa7134 cards. I had some issues with his original<br>patch, and I gave him some critique. I would not commit the patch for him even
<br>then, because I figured that some other eyes might see other issues. Yours, for<br>example.<br><br>He did not simply duplicate the code -- his card has the tuner on a different<br>i2c address. What do you suggest that he do instead?
<br><br>His card seems to be dvb-t only, he claims no analog support, but I have trouble<br>believing that, given that it uses a tda8275 tuner and a saa7131 bridge -- this<br>bridge has a tda8290 spliced into it. For sure the card must support analog tv,
<br>but he says there is no radio input, no svideo input and no composite input.<br><br>Feel free to make any suggestions, I will not commit any patch if people disagree.<br><br>Cheers,<br><br>Mike<br><br><br><br>------------------------------
<br><br>Message: 9<br>Date: Mon, 20 Aug 2007 02:03:47 +0200<br>From: hermann pitton <<a href="mailto:hermann-pitton@arcor.de">hermann-pitton@arcor.de</a>><br>Subject: Re: [linux-dvb] [PATCH] saa7134: add DVB-T support for
<br> Avermedia Super 007<br>To: <a href="mailto:bobbens@gmail.com">bobbens@gmail.com</a><br>Cc: <a href="mailto:video4linux-list@redhat.com">video4linux-list@redhat.com</a>, <a href="mailto:linux-dvb@linuxtv.org">
linux-dvb@linuxtv.org</a><br>Message-ID: <<a href="mailto:1187568227.4640.53.camel@pc08.localdom.local">1187568227.4640.53.camel@pc08.localdom.local</a>><br>Content-Type: text/plain<br><br>Am Sonntag, den 19.08.2007
, 23:39 +0200 schrieb hermann pitton:<br>> Hi,<br>><br>> quick patches are always fine :)<br>><br>> Am Sonntag, den 19.08.2007, 19:56 +0200 schrieb <a href="mailto:bobbens@gmail.com">bobbens@gmail.com</a>:<br>
> > Hello,<br>> ><br>> > After getting my card working I decided to hack up a patch to get<br>> > autodetection working. With mkrufky's guidance I was able to make a<br>> > patch he had few complaints of which I now include here.
<br>><br>> This suggests somehow that Mike is fine with what you have so far.<br>> I don't believe that.<br>><br>> We should not add new cards these days just by doing some code<br>> duplication with the first working testing case on saa7134-dvb.
<br>> (card=109)<br>><br>> Also this one should not be in the Philips Tigers eeprom detection IMHO.<br>><br>> We should know too, if it really has a LNA. The first guess working is<br>> no equivalent for removing the tuner shielding. At least a test with
<br>> config=0 should be done. Else we might stay in the dark, when more<br>> assured hardware knowledge is needed in the future.<br>><br>> Mike please take over/comment.<br><br>The pop3 of my mail provider is in delay. (copy/paste)
<br><br><br>> Hermann,<br>><br>> I showed him how to make a patch and suggested that he send it in to the mailing<br>> list for exactly this reason -- because I am not familiar with all the<br>> intricacies of the various saa7134 cards. I had some issues with his original
<br>> patch, and I gave him some critique. I would not commit the patch for him even<br>> then, because I figured that some other eyes might see other issues. Yours, for<br>> example.<br>><br>> He did not simply duplicate the code -- his card has the tuner on a different
<br>> i2c address. What do you suggest that he do instead?<br><br>Mike, kick me, for not thinking twice. Of course this was it all about!<br>And as long there is no tuner address detection on DVB-T, we need the<br>new config. Started with this Twinhan saa713x, followed by the CTX953
<br>and also this new Avermedia hybrid now. Hard these days to ack new<br>hardware without having it, but yes, this one needs a new config<br>currently in saa7134-dvb.<br><br>> His card seems to be dvb-t only, he claims no analog support, but I have trouble
<br>> believing that, given that it uses a tda8275 tuner and a saa7131 bridge -- this<br>> bridge has a tda8290 spliced into it. For sure the card must support analog tv,<br>> but he says there is no radio input, no svideo input and no composite input.
<br><br>Think we saw the new variant without DVB-T support already on the<br>video4linux-list. Analog video was working with the Avermedia Go 007<br>entry, no analog audio support, radio likely needs to be changed to amux
<br>TV, but with these new DVB-T variants, how to get analog initialization<br>seems not to be clear yet.<br><br>> Feel free to make any suggestions, I will not commit any patch if people disagree.<br><br>Should be added to DVB-T just now, but the existence of the LNA should
<br>also be tested with config=0, if this makes any difference. On a good<br>photo, the LNA should also become visible, since this one has no<br>shielding ... The remote looks like on the other Aver/initial_Medion<br>stuff, but can't identify the usual controller on the fuzzy pictures.
<br><br>If we have on the v4l-wiki and in comments, what is not yet supported,<br>we better move them in. To wait until _everything_ is perfect seems no<br>solution either. On the saa7133/35/31e only dual language support is
<br>missing, Soeren gets hangs after 5 days, still could be a bug ...<br><br>The driver is not clever enough for cardbus power handling and advanced<br>suspend modes, but else really not bad. Any help is welcome!<br><br>If we get trouble, we can at least share it.
<br><br>Cheers,<br>Hermann<br><br>Acked-by: Hermann Pitton <<a href="mailto:hermann-pitton@arcor.de">hermann-pitton@arcor.de</a>><br><br><br>> > This should get the DIGITAL part of the AVerMedia AVerTV DVB-T Super
<br>> > 007, as noted in the patch ANALOG isn't working. I do not have windows<br>> > installed and live in a pure linux environment (with bits of *BSD here<br>> > and there). I'll try to see what I can do with a bit of testing, trying
<br>> > some values for other cards (and hopefully not burning out mine). If<br>> > anyone has windows and this card, please do it instead.<br>> ><br>> > Haven't tested remote either, will get to that also soon.
<br>> ><br>> > -bobbens<br><br><br><br><br><br>------------------------------<br><br>_______________________________________________<br>linux-dvb mailing list<br><a href="mailto:linux-dvb@linuxtv.org">linux-dvb@linuxtv.org
</a><br><a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb">http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb</a><br><br>End of linux-dvb Digest, Vol 31, Issue 76<br>*****************************************
<br></blockquote></div><br>