> > It could do fancy copy stuff. There is someone looking at that currently.
>
> It should be as simple as adding the following to the tulip driver:
> { "Davicom DM9102", { 0x91021282, 0xffffffff },
> TULIP_IOTYPE, 0x80, DC21140 },
> { "Davicom DM9100", { 0x91001282, 0xffffffff },
> TULIP_IOTYPE, 0x80, DC21140 },
>
> I have this in my development version, but I don't have a Davicom card to
> test with. This also assumes that the EEPROM media table is correct for the
> board -- the Dmfe driver is the typical single-point driver that doesn't
> parse the EEPROM, but just picks out the fields that it wants.
Reading their driver that is evidentally not the case for all boards. Look
at the extra checksum handling fixups. The Davicom appears to be
"tulipish" for some parts anyway.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]