Hi, Am Mittwoch, den 11.03.2009, 14:44 -0300 schrieb Douglas Schilling Landgraf: > Hello, > > On Sun, 08 Mar 2009 01:45:36 +0100 > hermann pitton <hermann-pitton@xxxxxxxx> wrote: > > > Hi! > > > > Am Samstag, den 07.03.2009, 19:19 -0500 schrieb Andy Walls: > > > On Sat, 2009-03-07 at 19:06 -0500, Andy Walls wrote: > > > > On Sat, 2009-03-07 at 18:26 -0500, Devin Heitmueller wrote: > > > > > On Sat, Mar 7, 2009 at 5:45 PM, Douglas Schilling Landgraf > > > > > <dougsland@xxxxxxxxx> wrote: > > > > > > Hi Mauro, > > > > > > > > > > > > Please pull from: http://linuxtv.org/hg/~dougsland/v4l-dvb > > > > > > for the following: > > > > > > > > > > > > - v4l2-apps/util: Add rewrite_eeprom tool > > > > > > Modules this script is known to > > > > > > work with: em28xx and saa7134 > > > > > > > > > > > > Thanks, > > > > > > Douglas > > > > > > -- > > Added to the same tree new version of script: > > - A few improvements to initial version of script > - Added validations to avoid issues to users > - Added a huge red warning message > > IMO, the current version will cover those suggestions. If not, please > let me know. > > Thanks everyone, > Douglas seems to be safe to me on the saa7134 driver, but those pointing to further risks are welcome. The dual saa7134 PCI bridge devices in need of a correct eeprom are out of the game in the original dual/triple slots, even first and second bridge might be swapped compared to the m$ driver and so on. Those tools are around anyway, I remember the case of a manipulated eeprom we alredy had. (with one of Dmitry's devices, IIRC) On some mobo's with lots of saa713X devices the eeprom readout can be flaky sometimes. If it is only a single device likely the PSU is becoming faulty, just to remember to check against that too. If there is a known list of critical eeprom types and about cases we disabled the write protection, this would be good to know as well. Cheers, Hermann -- 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
