Em Mon, 09 Nov 2009 00:32:29 +0100 hermann pitton <hermann-pitton@xxxxxxxx> escreveu: > > I agree. An interesting case happens with devices that uses tda10046 DVB demods. > > They have the firmware stored internally on their eeprom. Those firmwares can be > > replaced by a different version loaded in ram, but, in general, they work > > properly with the eeprom one. So, even having the firmware load code there, > > the firmware at /lib/firmware is optional. > > Mauro, that could lead to some misunderstanding of the current use > conditions, at least on saa7134. > > Minor annotations, the tda10046 does not store firmware internally, but > there are cards which have an extra eeprom to store such firmware. > > If such a firmware eeprom is found and correctly configured, the driver > in all cases will load the firmware from that eeprom and all other > firmware in /lib/firmware is ignored. > > If not, the firmware will be loaded from /lib/firmware. > > For all what I know, firmware revisions 26 and 29 are both valid > "enough", correspondents to what we can load either from TechnoTrend or > LifeView with the getfirmware script, and might be either stored in an > extra eeprom or loaded from host/file. > > Prior revisions had issues with missing freqs, in what combination ever. > > We also can't totally exclude, given the whole mass of such, that in > some cases firmware eeproms might exist on some boards, but are not > correctly configured and load from host only because of that. > > The tendency seen overall is that competitors save the few cents for an > extra firmware eeprom these days ... Yes, I know. I have myself a Cardbus device with such eeprom (I think it has revision 29 stored at the eeprom). The point is that it is not mandatory for such devices to have a firmware at the filesystem for the device to work. So, a static indication that devices with tda10046 need firmware is wrong, since some devices don't need it. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
