From: Bart Vandewoestyne <Bart.Vandewoestyne@pandora.be>
To: Camiel Vanderhoeven <camiel_toronto@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DOS2linux
Date: Tue, 28 Aug 2001 17:03:21 +0200 [thread overview]
Message-ID: <3B8BB2B9.302F6485@pandora.be> (raw)
In-Reply-To: <001101c12fd0$0fd7f9c0$0100a8c0@kiosks.hospitaladmission.com>
Camiel Vanderhoeven wrote:
>
> Did you do a normal read from memory, or did you use port-i/o?
I used the inb() function.
> you should use the latter. Of course, your card could be at 2000h in
> stead of 1000h, or at X000h for that matter.
My card is at 1000h, that's something i know for sure, because I can
probe the EISA ID at 0x1000+0xc80.
> I'm not very familiar with
> the EISA architecture, but I do know that each card can use the
> following I/O ranges:
> X000h-X0FFh; X400h-X4FFh; X800h-X8FFh; XC00-XCFF, where X is the slot
> number.
I guess you mean X0000h-X0FFF; X1000-X1FFF; ...
> There is a book on the EISA architecture available free of
> charge as a PDF file from www.mindshare.com/pdf/eisabook.pdf. Perhaps
> you'll find what you need to know from studying that. I hope this helps.
Tnx for the tip! I will check it out!
I also found this URL: http://uw7doc.sco.com/cgi-bin/man/man?eisa+D4
It comes from UnixWare 7 documentation and there they have the kind of
translation that I want to do (that is: translate INT 15h call "Read
Function" (AH=D8h, AL=01h)) to linux. As i understood there isn't
such thing available for linux? Meaning I'll have to try and
implement that stuff myself? But then the problem remains: how do i
get to the data that is in the 320 byte buffer returned from an INT
15h call "Read Function" (AH=D8h, AL=01h)
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-28 15:03 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 ` DOS2linux Bart Vandewoestyne
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 ` Bart Vandewoestyne [this message]
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=3B8BB2B9.302F6485@pandora.be \
--to=bart.vandewoestyne@pandora.be \
--cc=camiel_toronto@hotmail.com \
--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