Messages in this thread | | | Subject | Re: DOS2linux | Date | Mon, 27 Aug 2001 21:28:55 +0100 (BST) | From | Alan Cox <> |
| |
> Hmm... with 'writing cleanly' you mean that there should become things > available like eisa_register_device() etc...?
Yeah
> > EISA slots are I/O mapped at 0x1000, 0x2000, 0x3000, 0x4000 -> 0x8000 > > The ID port is at base+0xc80 > > Configuration data follows at base+0xc84, 0xc88 ... > > Yep, that was also what I figured out. > > > I would assume the 320 byte buffer is providing this same data block, and > > maybe more but I don't know the details. > > That is also what I think, but the problem is that I don't know at > which offset to look for that data... > If you look at the code: > > Would it help if i told you that itconf and dmachd are defined as (see > http://mc303.ulyssis.org/heim/downloads/DISCINC.H ) > > #define itconf 0xb2 > #define dmachd 0xc0 > > So if my EISA board is at 0x1000, i should be able to read these > values from 0x1000+0xb2 and 0x1000+0xc0 ??? And if 'yes', any idea > about how to read them? (byte, word, long...? My guess would be as a > byte, but I'm not sure...) >
Wild guess. Try iobase + 0xC80 to check if the card is in that slot, then check inb(iobase+0xC80+0xb2) and see if that gives sane answers - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |