On Tue, Aug 11, 2009 at 4:24 PM, <xwang1976@xxxxxxxx> wrote: > Hi to all! > I don't know why, but today my device has changed its EEPROM hash to the > following value 0x396a0441 > as you can see from the attached dmesg. > So it is not recognized anymore. > Is there something that can cause such a change? > I suspect it is not the first time that the eprom hash of this device > change. > Can you help me? > Xwang > > PS Meantime I will change the hash and test if the device work again. Comparing the two eeprom dumps (the one from your previous email versus the one you just sent), it would appear that something resulted in the value 0xFF written to offset 0xF0. What were you doing immediately prior to the failure? I'm not sure how we could have gotten into this state. Douglas, in a few minutes I am leaving town for the next five days. Can you help Xwang out to restore his eeprom content using your tool? Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
