In article <20000719154955.U21194@valinux.com>,
David Hinds <dhinds@valinux.com> wrote:
>I think the problem is that the CardBus bridge setup code in 2.4 only
>allocates 256 bytes of IO space, total, per socket, and this card
>requires two 256-byte IO windows, one for each device. So the
>allocation for resource 0 for the second device (the modem) fails.
>
>I tried poking around to figure out where this is set but I couldn't
>find it. Martin probably knows exactly where to look.
>
>Hmmm. Actually, now that I think about it, maybe this is not so easy
>as bumping a limit up from 0x100 to 0x200. The IO port allocation
>code in 2.4 assumes that the only safe IO port regions for PCI devices
>are 0x400-0x4ff, 0x800-0x8ff, 0xa00-0x8ff, etc. A card like this that
>needs >256 ports will need to have them split up into non-contiguous
>pieces. However, the resource manager expects a PCI bus to have a
>single parent IO resource that can get cut up in any arbitrary way.
Hmm.. The 256-byte limitation was something I was wondering about:
there's really not all that strong a reason for it these days, and I
_think_ a PCI decode should override a old-time ISA decode anyway.
So we might change the 256-byte check into a warning rather than an
error.. Martin?
Linus
-
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/
This archive was generated by hypermail 2b29 : Sun Jul 23 2000 - 21:00:13 EST