public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: "'H. Peter Anvin'" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: The latest instance in the A20 farce
Date: Wed, 10 Jan 2001 16:09:38 -0800	[thread overview]
Message-ID: <3A5CF9C2.CE5EFF42@transmeta.com> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBDEF6@orsmsx31.jf.intel.com>

"Dunlap, Randy" wrote:
> 
> a. The BIOS isn't required to have int. 0x15, AH=0x2401 [Appx. A],
>    but that is handled by your patch.

Idiots.  This should be required and be a null function; likewise
AH=0x2400.  The only thing that the current spec means is that 

> b. The BIOS isn't required to have int. 0x15, AH=0x88 [Appx. A]
>    (Ye Olde Traditional memory-size function).

Incorrect; see page 226.

>    Hopefully the other memory-size methods will always have
>    priority.
> c. A20M# is always de-asserted at the processor [Ch. 3, item SYS-0047]
> 
> I bring these up because they may have some impact on SYSLINUX,
> LILO, etc., and the data structures that they use (like the
> memory_size item) and because some of these systems don't
> have a "real mode," so loaders can't reliably assume that
> they do (unless it's transparent to the loaders)...
> and because you know something about SYSLINUX etc.
> 

URRRK.  I get a feeling these specs are either there to make life extra
difficult for programmers, because the people that design them are too
stupid to tie their own shoes, or because they want nothing but M$
factory-installed to work.  

A20M# always deasserted: this is all fine and good if we had nothing else
to worry about, but they really have managed to fuck up when it comes to
getting something to work *ACROSS THE BOARD*.  THEY DON'T GIVE ME A WAY
TO DETECT THE FACT THAT A20M# IS FIXED!!!!!  This is particularly nasty
when going back to real mode, since I don't have a way to figure out that
I can't turn A20M# back to its old state.  

I also really, really, *REALLY* hate them for killing serial ports.  It's
a Bad Idea[TM].

Worse, they define that port 92h, bit 1, is no longer A20M#... but they
don't forbid the system from using it for other things.

	-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/

  reply	other threads:[~2001-01-11  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10 23:56 The latest instance in the A20 farce Dunlap, Randy
2001-01-11  0:09 ` H. Peter Anvin [this message]
2001-01-11 10:32   ` Olaf Titz
2001-01-15 17:24   ` Maciej W. Rozycki
2001-01-15 17:44     ` H. Peter Anvin
2001-01-15 19:30       ` Albert D. Cahalan
2001-01-15 20:00         ` H. Peter Anvin
2001-01-18 12:21           ` Gerhard Mack
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11  1:43 Dunlap, Randy
2001-01-11  1:59 ` H. Peter Anvin
2000-12-06 23:55 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=3A5CF9C2.CE5EFF42@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@intel.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