Hi all,
Oliver Endriss wrote:
> Chris Dietrich wrote:
>>What does the return value of -5 (which seems to be returned by the
>>i2c_transfer AFAIK) mean?
> The stv0299 did not respond, i.e. was not found on the I2C bus.
>>I also found out, that if I load the kernel 2.4 stv0299 driver (and
>>budget-av etc...) and use the card, then warm reboot the machine into a
>>2.6 kernel, no error appears and the card works fine!
>>So, this sounds like an initialization error, right?
> Yes.
> Try the following:
> (a) enable master reset in saa7146_core.c
> If it does not help:
> (b) Add some delay at the beginning of stv0299_attach.
> Something like msleep(1000) should do for testing.
OK, I tried both and am still getting an error, but now the failing
writeregI-call returns -121 and no longer -5 (see below). (btw: where
can I lookup these return codes?)
Nov 9 18:46:40 linux kernel: saa7146: found saa7146 @ mem d0c34c00
(revision 1, irq 9) (0x1131,0x4f56).
Nov 9 18:46:40 linux kernel: DVB: registering new adapter (KNC1 DVB-S).
Nov 9 18:46:40 linux kernel: adapter failed MAC signature check
Nov 9 18:46:40 linux kernel: encoded MAC from EEPROM was
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
Nov 9 18:46:40 linux kernel: budget-av: ci interface initialised.
Nov 9 18:46:40 linux kernel: KNC1-0: MAC addr = 00:09:d6:40:...
Nov 9 18:46:41 linux kernel: stv0299: stv0299_writeregI: writereg error
(reg == 0x02, val == 0x34, ret == -121)
^^^^
Nov 9 18:46:41 linux kernel: stv0299: stv0299_readreg: readreg error
(reg == 0x00, ret == -5)
Nov 9 18:46:41 linux kernel: budget-av: A frontend driver was not found
for device 1131/7146 subsystem 1131/4f56
> If it does't help either you should compare the initialization code of
> the old driver with the new one. Maybe the frontend power is not
> turned-on for this card. This is usually done by switching some GPIO
> line. See frontend_init() in budget-av.c.
OK, thanks. I will try to do that.
I have commented out the only GPIO call in frontend_init in budget-av
saa7146_setgpio(saa, 3, SAA7146_GPIO_OUTHI);
just to see whether it would produce the same error (-121 on writeregI)
and this is true, but probably this just confirms that the frontend
power is not turned on.
-chris
