mv6360 support in mv64x60.c (was Re: GT64260_eth (Ethernet) Driver)

[David Woodhouse]

More progress... the IRQ code works a bit better if it's ic_bh->v_addr
is at offset zero in the chip instead of the 0xc18 which is correct only
for the GT64260. The host bridge itself appears on the bus as device #3,
which is why we couldn't autodetect it by looking at vendor/device of
device #0.

∃ an Ethernet driver for the MV64340 (the MIPS version of the chip). It
doesn't use OCP though -- there's no OCP on MIPS. Can someone explain
why OCP is used instead of the generic platform_device functionality
provided by the kernel? Should we convert MIPS to OCP?

--
dwmw2


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/