> Hum. It should be reporting the physical address of each port now. The
> pci_scan code passes that to the drivers. What dpes ot show ?
Well, I must have been on crack; I probably did the test on another
patch iteration. Taking your 2.3.18ac10 patch and changing TULIP_SIZE
to be 0x80 I get the following from dmesg:
3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c900 Boomerang 10baseT at 0xec00, 00:10:4b:b3:8a:92, IRQ 11
8K word-wide RAM 3:5 Rx:Tx split, autoselect/10baseT interface.
Enabling bus-master transmits and whole-frame receives.
eth1: Digital DC21041 Tulip rev 33 at 0xea000000, 00:C0:F0:37:22:56, IRQ
11.
eth1: 21041 Media table, default media 0800 (Autosense).
eth1: 21041 media #0, 10baseT.
eth1: 21041 media #4, 10baseT-FD.
tulip.c:v0.91m 9/15/99 becker@cesdis.gsfc.nasa.gov
[root@wr5z /root]# cat /proc/iomem
00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-03ffffff : System RAM
00100000-00200ea7 : Kernel code
00200ea8-00218f73 : Kernel data
e0000000-e3ffffff : VIA Technologies VT 82C597 Apollo VP3
e4000000-e4ffffff : ATI Mach64 GB
e6000000-e6000fff : ATI Mach64 GB
e8000000-e803ffff : DEC DC21041
e9000000-e900ffff : 3Com 3C900 10bTPO
ea000000-ea00007f : DEC DC21041
ea000000-ea00007f : eth1
That looks a lot more reasonable than what I remember. I understand the
ea000000-ea00007f part. I'm a little unclear on what it's telling me
about e8000000-e803ffff and e9000000-e900ffff though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/