>>>>> "Joseph" == Joseph CHANG <josright123@xxxxxxxxx> writes:
> Add to maintain variant eeprom adapters which may have not right
> dm962x's format.
> Signed-off-by: Joseph CHANG <josright123@xxxxxxxxx>
> +static void dm_render_begin(struct usbnet *dev)
> +{
> + /* Render eeprom if need, WORD3 render, set D[15:14] 01b */
> + dm_eeprom_render(dev, 3, 0x4000, 0xc000);
> + /* Render eeprom if need, WORD7 render, clear D[10] */
> + dm_eeprom_render(dev, 7, 0x0000, 0x0400);
> + /* Render eeprom if need, WORD11 render, need 0x005a */
> + dm_eeprom_render(dev, 11, 0x005a, 0xffff);
> + /* Render eeprom if need, WORD12 render, need 0x0007 */
> + dm_eeprom_render(dev, 12, DM_EP3I_VAL, 0xffff);
With render I guess you mean something like fixup? I'm not sure we want
to do this automatically without an explicit action from the user.
How common are these adapters without valid eeprom? What happens if the
eeprom content isn't fixed?
Do we need to reset the device once the eeprom is updated?
--
Bye, Peter Korsgaard
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
