From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: setup.S: A20 enable sequence (once again)
Date: 6 Nov 2000 14:06:04 -0800 [thread overview]
Message-ID: <8u7a0c$p4u$1@cesium.transmeta.com> (raw)
In-Reply-To: <8u6vn8$70i$1@cesium.transmeta.com> <E13stqG-0006eJ-00@the-village.bc.nu>
Followup to: <E13stqG-0006eJ-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> > This doesn't really work. Neither the fast A20 gate nor the KBC is
> > guaranteed to have immediate effect (on most systems they won't.)
>
> Fast A20 gate happens to be immediate on all the embedded kit I know so its
> probably acceptable, and if its too slow it still does the kbc timeout. Since
> its generally on chip they dont muck about talking to keyboard and other junk
> I/O controllers.
>
I'd rather do it "right", which is to poll for A20 in the same loop as
we wait for the KBC to become available.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 16:50 setup.S: A20 enable sequence (once again) Robert Kaiser
2000-11-06 19:10 ` H. Peter Anvin
2000-11-06 21:30 ` Alan Cox
2000-11-06 22:06 ` H. Peter Anvin [this message]
2000-11-06 19:56 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2000-11-06 19:29 Robert Kaiser
2000-11-06 20:16 ` H. Peter Anvin
[not found] <200011062003.VAA11818@rob.devdep.sysgo.de>
2000-11-06 20:20 ` Robert Kaiser
2000-11-06 20:43 ` H. Peter Anvin
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='8u7a0c$p4u$1@cesium.transmeta.com' \
--to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.