Re: 2.4.0-test2: multiple 3c509s problem and dumb fix

[Andrew Morton]

[e-mail] wrote:
> 
> Hi,
> 
> I've been booting with the test2 kernel on a P133 box with two
> ISA (I think non-PnP) 3c509s in it. It boots up fine, but the 3c509
> driver is reporting if_port as BNC when it is 10BaseT (and correctly
> reported as that by the normal running kernel, 2.2.12) This appears
> to stem from a change in the value of dev->mem_start when first used
> by the 3c509 driver, in particular the expression
> 
>       (dev->mem_start & 0x1f)

Pete, several of the net drivers overload the meaning of the mem_start
argument in the 'ether=' argument to mean soemthing totally different.

3c509 does this.  It uses the lower two bits of mem_start to select the
interface (!).  The mem_start arg has nothing to do with memory
addressing for 3c509.

you need to provide a boot arg of the form

  ether=IRQ,base_addr,mem_start,mem_end,name

or

  ether=10,0x300,0,0,eth0

to select interface type 0.

The most up-to-date docco on this is in
Documentation/m68k/kernel-options.txt, of all places.

I suggest you play with the ether= options a bit further.