Re: 2.3.18ac9 doesn't detect tulip (again!)

Thomas Molina (tmolina@home.com)
Mon, 27 Sep 1999 16:27:02 -0500 (CDT)


On Mon, 27 Sep 1999, Matti Aarnio wrote:
> On Mon, Sep 27, 1999 at 03:02:33AM -0500, Thomas Molina wrote:
> > I looked into this problem again after appearance of 2.3.18ac9 (BTW, the
> > EXTRAVERSION in the ac9 patch still says ac8). I didn't have any luck,
> > but, by increasing debug levels, I found what I hope is a clue for my
> > betters.
>
> Maybe, maybe not.
>
> Show us the result of: cat /proc/iomem
> about the range data for 21041 chip.

00000000-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-03ffffff : System RAM
00100000-002006e7 : Kernel code
002006e8-002189d3 : 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

> > Found 3c900 Boomerang 10baseT at PCI address 0xec00, IRQ 11.
> > Found Digital DC21041 Tulip at PCI address 0xea000000, IRQ 11.
> > Is the 0xe800 vs 0xea00 significant? I'm clueless here.
>
> The addresses are IO: 0xe800 vs. MEM: 0xea000000
> they are of DIFFERENT IO facilities.

Doh! That's what I get for trying to debug something at 3AM when I
can't sleep. I had read the comment in Donald's code too!:

/* This driver was originally written to use I/O space access, but now
uses memory space by default. Override this this with -DUSE_IO_OPS.
*/

lspci says this:

00:08.0 Ethernet controller: Digital Equipment Corporation DECchip 21041
[Tulip Pass 3] (rev 21)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 set
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e800
Region 1: Memory at ea000000 (32-bit, non-prefetchable)

-
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/