Date: Tue, 24 Apr 2007 13:29:04 -0400 From: "Jim Stapleton" <stapleton.41@gmail.com> To: "Greg 'groggy' Lehey" <grog@freebsd.org> Cc: freebsd-multimedia@freebsd.org Subject: Re: pvrxxx, linux code and modules Message-ID: <80f4f2b20704241029x68e18eddgad417a71195d2666@mail.gmail.com> In-Reply-To: <20070424001346.GF45246@wantadilla.lemis.com> References: <c39ec84c0704151508t126cf975gaa1957b9205d3244@mail.gmail.com> <80f4f2b20704230529s706c50a9pa4716e74c2b04182@mail.gmail.com> <20070424001346.GF45246@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have a question regarding the tuner identification process... Namely, what are the pieces pieces of identification are needed to identify the tuner, and how uniform are they between card make/models? ex: In the driver I see a 1 byte eeprom code (Eh), and a 1 byte tuner code (Th). 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? I'm just curious how much more data will need to be packed into the text entries on the files... And how much can be put there to make the tuner drivers as generic as possible (theoritically, it'd be nice to have one tuner driver that would work with any television/radio card, which would be able to determine the tuner, without the other drivers having to do calculations on the eeprop/card data). Thanks, -Jim Stapleton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80f4f2b20704241029x68e18eddgad417a71195d2666>