Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: diffrence between manufactures



Clemens Kirchgatterer writes:
 > this is the output of syslogd after executing "make insmod" in
 > DVB/driver/
 > 
 > Sep 26 18:35:26 love kernel: i2c-core.o: i2c core module
 > Sep 26 18:35:26 love kernel: Linux video capture interface: v1.00
 > Sep 26 18:35:26 love kernel: saa7146_init_one()
 > Sep 26 18:35:26 love kernel: i2c-core.o: adapter saa7146(1) registered as adapter 0.
 > Sep 26 18:35:26 love kernel: saa7146_core.o: saa7146(1): bus:0, rev:1, mem:0xc586e000.
 > Sep 26 18:35:26 love kernel: i2c-core.o: driver VES1893 DVB DECODER registered.
 > Sep 26 18:35:26 love kernel: VES1893: init_module
 > Sep 26 18:35:26 love kernel: i2c-core.o: driver VES1820 DVB DECODER registered.
 > Sep 26 18:35:26 love kernel: VES1820: init_module
 > Sep 26 18:35:28 love kernel: i2c-core.o: driver dvbi2c registered.
 > Sep 26 18:35:28 love kernel: wait-for-debi-done maxwait: 500000
 > Sep 26 18:35:28 love kernel: bootarm: debi test failed!!
 > Sep 26 18:35:28 love kernel: dvb: firmware = 00000000
 > Sep 26 18:35:28 love kernel: dvb: MAC = 00 d0 5c 88 63 81 
 > Sep 26 18:35:28 love kernel: dvb: attach_adapter
 > Sep 26 18:35:28 love kernel: dvb: 1 dvb(s) found!
 > Sep 26 18:35:28 love kernel: i2c-core.o: driver i2c TV tuner driver registered.
 > Sep 26 18:35:29 love kernel: i2c-core.o: driver i2c msp3400 driver registered.
 > 
 > btw: i've added msp3400 to the OBJS macro in the Makefile as it
 > seemed to be missing.
 > 
 > looks like there is no firmware, right?


Yes, but not for the same reason as in other cases.

The firmware (at least the application part, the firmware core is
in ROM on-chip) is normally loaded by the driver during init.
The firmware is written through the so-called DEBI-port of the SAA7146
into a dual-ported RAM and from there into DRAM which is used directly
by the AV7110.
At the beginning of the firmware download routine the DEBI-port writes
some bytes to the dual-ported RAM and reads them back to test the
DEBI-port. This basic test failed in your case!

> Sep 26 18:35:28 love kernel: bootarm: debi test failed!!

This is not good and indicates a hardware problem, either with
the SAA7146, or the dual-ported RAM. 

Since all those cards are really identical I also cannot think of
another reason for this problem, like e.g. timing problems or use of 
different components, etc.

Did you try this card using Windows with drivers from Galaxis? Does it work there?
If not I would strongly suggest to have a talk with the person you
bought it from. You said you got it at ebay?

Ralph


Home | Main Index | Thread Index