Since you are talking about tda182x, I have had some issues in this
area, and some with the i2c setup too.
I have a lifewalker usb dual digital tuner, which uses
tda827x 8324 2
tda1004x 17028 2
dvb_usb_m920x 18308 1
I was using b16ef95c0418/5894 on top
On Nov 20, 2007 6:23 AM, Scott Merrilees [EMAIL PROTECTED] wrote:
Since you are talking about tda182x, I have had some issues in this
area, and some with the i2c setup too.
I have a lifewalker usb dual digital tuner, which uses
tda827x 8324 2
tda1004x 17028 2
MikeW wrote:
Michael Krufky mkrufky at linuxtv.org writes:
You might want to take a look at the tda18271 driver recently merged
into the master branch, located under dvb/frontends ...
Perhaps this driver might be enough to bring up the tda18211-- I don't
have the spec for the 18211, so I
MikeW wrote:
Michael Krufky mkrufky at linuxtv.org writes:
It's not wrong -- it's just missing.
I said it before -- the driver is not tested with DVB-T --
I need a test case for it first. Feel free to send in a
patch, since you DO have that test case.
Cheers,
Mike Krufky
Sadly I
On 11/8/07, Michael Krufky wrote:
If you prefer, I can arrange for a separate repository to be set up
for the purposes of the tda182x1 work.
Let me know what you think.
I used gmail to write that message, but forgot to change the return
address to linuxtv.org -- please use my linuxtv.org
On 11/8/07, MikeW [EMAIL PROTECTED] wrote:
Michael Krufky mkrufky at linuxtv.org writes:
You might want to take a look at the tda18271 driver recently merged
into the master branch, located under dvb/frontends ...
Perhaps this driver might be enough to bring up the tda18211-- I don't
Michael Krufky mkrufky at linuxtv.org writes:
On 11/1/07, MikeW mw_phil at yahoo.co.uk wrote:
Using the OM5776 eval board, and using the algorithm published
in the rev 1.1.0 datasheet, I find I am getting an I2C NAK,
which does not go away and requires a chip reset to restore
any I2C
Using the OM5776 eval board, and using the algorithm published
in the rev 1.1.0 datasheet, I find I am getting an I2C NAK,
which does not go away and requires a chip reset to restore
any I2C communication, after successfully writing EP4 (r06) in the
'image rejection cal pt I, wanted signal
On 11/1/07, MikeW [EMAIL PROTECTED] wrote:
Using the OM5776 eval board, and using the algorithm published
in the rev 1.1.0 datasheet, I find I am getting an I2C NAK,
which does not go away and requires a chip reset to restore
any I2C communication, after successfully writing EP4 (r06) in the
