From: "Pedro M. Rodrigues" <pmanuel@myrealbox.com>
To: John Heil <kerndev@sc-software.com>, root@chaos.analogic.com
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
Subject: Re: IO delay, port 0x80, and BIOS POST codes
Date: Thu, 14 Mar 2002 22:19:23 +0100 [thread overview]
Message-ID: <3C9121EB.11632.26F0805@localhost> (raw)
In-Reply-To: <Pine.LNX.4.33.0203141234170.1286-100000@scsoftware.sc-software.com>
In-Reply-To: <Pine.LNX.3.95.1020314155816.136A-100000@chaos.analogic.com>
This piece of code is taken from an old Minix source code tree, the file being
boothead.s . Notice the port 0xED usage and the comment.
! Enable (ah = 0xDF) or disable (ah = 0xDD) the A20 address line.
gate_A20:
call kb_wait
movb al, #0xD1 ! Tell keyboard that a command is coming
outb 0x64
call kb_wait
movb al, ah ! Enable or disable code
outb 0x60
call kb_wait
mov ax, #25 ! 25 microsec delay for slow keyboard chip
0: out 0xED ! Write to an unused port (1us)
dec ax
jne 0b
ret
kb_wait:
inb 0x64
testb al, #0x02 ! Keyboard input buffer full?
jnz kb_wait ! If so, wait
ret
/Pedro
On 14 Mar 2002 at 16:03, Richard B. Johnson wrote:
>
>
> Well I can see why he's an EX-Phoenix BIOS developer. A port at 0xed
> does not exist on any standard or known non-standard Intel/PC/AT
> compatible.
>
> Remember DOS debug?
>
> C:\>debug
>
> -i ed
> FF
> -o ed aa
> -i ed
> FF
> -o ed 55
> -i ed
> FF
> -q
>
>
> This is not a DOS emulation. This is a real-mode boot where any ports
> will be visible. If you used it with success, it means that you didn't
> need the I/O delay of writing to a real port. Instead you got the few
> hundred nanoseconds of delay you get by writing to nowhere.
>
> Cheers,
> Dick Johnson
next prev parent reply other threads:[~2002-03-14 21:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 17:11 IO delay, port 0x80, and BIOS POST codes Martin Wilck
2002-03-14 17:54 ` Richard B. Johnson
2002-03-14 18:10 ` Alan Cox
2002-03-14 19:23 ` Linus Torvalds
2002-03-14 19:46 ` H. Peter Anvin
2002-03-14 20:43 ` John Heil
2002-03-14 21:03 ` Richard B. Johnson
2002-03-14 21:19 ` Pedro M. Rodrigues [this message]
2002-03-14 21:26 ` John Heil
2002-03-14 21:41 ` Richard B. Johnson
2002-03-14 21:26 ` Linus Torvalds
2002-03-14 21:44 ` Richard B. Johnson
2002-03-14 21:56 ` H. Peter Anvin
2002-03-14 22:11 ` Richard B. Johnson
2002-03-14 22:20 ` H. Peter Anvin
2002-03-14 22:25 ` Richard B. Johnson
2002-03-14 22:58 ` Alan Cox
2002-03-14 22:56 ` Alan Cox
2002-03-14 21:11 ` H. Peter Anvin
2002-03-14 21:24 ` Linus Torvalds
2002-03-14 21:57 ` H. Peter Anvin
2002-03-14 22:06 ` John Heil
2002-03-14 22:55 ` Alan Cox
2002-03-14 22:39 ` John Heil
2002-03-14 23:29 ` Alan Cox
2002-03-15 0:12 ` David Golden
2002-03-15 0:11 ` John Heil
2002-03-19 14:25 ` Pavel Machek
2002-03-15 11:30 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 18:18 Thunder from the hill
2002-03-15 11:46 ` Martin Wilck
[not found] <3C90E983.5AC769B8@ngforever.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0203151243430.1477-100000@biker.pdb.fsc.net.suse.lists.linux.kernel>
2002-03-15 11:51 ` Andi Kleen
2002-03-15 12:47 ` Martin Wilck
2002-03-15 12:52 ` Andi Kleen
2002-03-15 15:07 Thunder from the hill
2002-03-15 17:39 Gerald Champagne
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=3C9121EB.11632.26F0805@localhost \
--to=pmanuel@myrealbox.com \
--cc=Martin.Wilck@fujitsu-siemens.com \
--cc=kerndev@sc-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=torvalds@transmeta.com \
/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