From: Bart Vandewoestyne <Bart.Vandewoestyne@pandora.be>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: DOS2linux
Date: Mon, 27 Aug 2001 22:19:10 +0200 [thread overview]
Message-ID: <3B8AAB3E.1EC121EA@pandora.be> (raw)
In-Reply-To: <E15bSeL-0004b3-00@the-village.bc.nu>
Alan Cox wrote:
>
> Oh god, thats the deep magic EISA weirdness department
*gnarf* ;-) Not good for a beginner like me I assume? :-(
> Well actually its one of those things that needs writing cleanly but
> currently appears in its own form in some EISA drivers
Hmm... with 'writing cleanly' you mean that there should become things
available like eisa_register_device() etc...?
> 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:
static int getslotinfo( void )
{
static char buff[320], *s=&buff[0]; int valid;
inregs.h.ah=0xd8; inregs.h.al=0x1; inregs.h.cl=DiSC_Id.slot>>12;
inregs.h.ch=0;
sregs.ds=FP_SEG(s); inregs.x.si=FP_OFF(s);
int86x(0x15, &inregs, &outregs, &sregs);
valid=outregs.h.ah;
if(!valid) { DiSC_Id.it=buff[itconf]; DiSC_Id.dma=buff[dmachd]; }
return(valid);
}
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...)
> I thought EISA boards had gone away
Unfortunately... the device I am trying to write a driver for is
especially designed for our university. Not many of those boards
exist in the world I guess :-(
(I hope that last sentence didn't take away your interest in my
project ;-)
Greetzzz,
mc303
--
Ing. Bart Vandewoestyne Bart.Vandewoestyne@pandora.be
Hugo Verrieststraat 48 GSM: +32 (0)478 397 697
B-8550 Zwevegem http://users.pandora.be/vandewoestyne
----------------------------------------------------------------------
"Any fool can know, the point is to understand." - Albert Einstein
next prev parent reply other threads:[~2001-08-27 20:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 19:39 DOS2linux Bart Vandewoestyne
2001-08-27 19:59 ` DOS2linux Randy.Dunlap
2001-08-27 20:06 ` DOS2linux Alan Cox
2001-08-27 20:19 ` Bart Vandewoestyne [this message]
2001-08-27 20:28 ` DOS2linux Alan Cox
2001-08-27 23:39 ` DOS2linux Camiel Vanderhoeven
2001-08-28 6:54 ` DOS2linux Bart Vandewoestyne
2001-08-28 14:45 ` DOS2linux Camiel Vanderhoeven
2001-08-28 15:03 ` DOS2linux Bart Vandewoestyne
2001-08-28 15:30 ` DOS2linux Brian Gerst
2001-08-27 22:23 ` DOS2linux Dr. Kelsey Hudson
-- strict thread matches above, loose matches on Subject: below --
2001-08-28 15:10 DOS2linux Camiel Vanderhoeven
2001-08-28 15:27 ` DOS2linux Camiel Vanderhoeven
2001-09-04 9:02 Dos2Linux Bart Vandewoestyne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B8AAB3E.1EC121EA@pandora.be \
--to=bart.vandewoestyne@pandora.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox