Second ethernet port

Hi Gary,

> trying to hack the kernel a bit and get some testing done.

I took a closer look myself ... as it turns out it looks like the driver will

only work with a single device since it stops probing once it finds the

first device.

> the kernel maps the first port to does not match the actual HW address.

If the address is 0x300 higher than you expect, this is normal as that is

where the registers are actually located.

> Any suggestions for values?

If all you want to do is test the second device (e.g. HW DVT), you can just

hardcode the values as the first entries in the tables. This way, your second device,

if present & detected will always be selected in lieu of the first device. (remember to

use the address of the registers). Otherwise, the driver code will need to be

updated to support more than a single device.

Regards,

--Scott