pvrxxx, linux code and modules

[Greg 'groggy' Lehey]

On Thursday, 26 April 2007 at 23:10:16 -0700, John-Mark Gurney wrote:
> Greg 'groggy' Lehey wrote this message on Fri, Apr 27, 2007 at 15:17 +0930:
>>> Is it safe to assume that with these two codes, the tuner will always
>>> be identifiable? (i.e. lets say a Leadtek card uses the same tuner,
>>> will I be able to take one byte from the Leadtek eeprom for it's
>>> eeprom code (El), and one byte for it's tuner code (Tl), and be able
>>> to determine the tuner, or might I need multiple bytes for El and/or
>>> Tl? Will they always be integers? Could strings be expected?
>>
>> My problem is that I don't know much about the tuners myself.  That's
>> a thing I'm planning to do when I have time.  Judging by the lack of
>> response from others, I'd guess that they don't have a definitive
>> answer either.  But from what I've heard, I suspect it's a good idea
>> not to rely on anything.
>
> Usually tuners are broken into two parts... One is the RF side of
> things that takes the antenna in, and tunes in the channel, and
> converts it down to base band signal, 0-6Mhz instead of 54-60Mhz...
> Then there is the demodulator that takes the base band signal in
> and converts it to the digital signal that the card then buffers
> and transfers to the PCI bus...  Usually the RF and demodulator are
> at different i2c address...
>
> Does this give you what you want?

Not really.  I'm looking for much more detail, something that driver
writers can use to actually write a driver.

I've started documenting the structure of the bktr driver.  It'll take
a while, but when I have a draft worth looking at, I'll make it
available.

Greg
--
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-multimedia/attachments/20070501/f7a71d20/attachment.pgp