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