Re: 2.1.103 MSS?

Alan Cox (
Fri, 22 May 1998 16:51:47 +0100 (BST)

> device/resource being busy.) BTW, that message (device busy) is
> almost no help since it doesn't say which thing it is that is having
> problems (IRQ, DMA, whatever)....

The message is unfortunately beyond my control. It does log things
if it sees a device but it is busy so that generally means "not found"

> applied to me: the IO of my card is 0x530 but the Crystal driver
> doesn't work at that port. If I set it to 0x534, it works fine. I

0x534 is where the chip sits. 0x530 is probalby where the I/O decode
starts. I've no idea why MSS sits at 0x534 but it does

> So it appears that the documentation ought to be updated to document
> this procudure. It took me quite awhile to figure out that ad1848 was
> part of the MSS (nowhere did the docs say that to load MSS, you load
> the ad1848 module). I would suggest that perhaps Readme.Cards or
> wherever these things go be updated with this info.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to