All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Werner Almesberger <wa@almesberger.net>
Cc: linux-kernel@vger.kernel.org, John Coffman <johninsd@san.rr.com>
Subject: Re: Kernel & BIOS return differing head/sector geometries
Date: Tue, 24 Jun 2003 08:29:20 -0700	[thread overview]
Message-ID: <3EF86E50.20504@zytor.com> (raw)
In-Reply-To: <20030624081319.G1326@almesberger.net>

Werner Almesberger wrote:
> H. Peter Anvin wrote:
> 
>>Presumably "linear", not "lba32".  I *presume* LILO has enough 
>>wherewithal to use EBIOS if it's available and fall back to CBIOS 
>>otherwise for at least one of these options.  I at least thought "lba32" 
>>would force EBIOS usage.
> 
> 
> Yes, that seems to be the case. (All the LBA32 code is from John
> Coffman. I've copied him in case he's interested in the thread.)
> But you're still betting on the BIOS to either implement EDD
> correctly, or at least to report that it doesn't support it.
> 
> Call me paranoid, but I wouldn't be at all surprised if there are
> some BIOSes out there that get this wrong.
> 

Well... it's somewhat unlikely given the sheer amount of things that 
would probably break.  The rule these days is that if it works with the 
particular versin of M$ that's currently shipping then it's good, but 
I'm pretty sure NTLOADER uses EDD.

	-hpa



  reply	other threads:[~2003-06-24 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 23:09 Kernel & BIOS return differing head/sector geometries Luis Miguel Garcia
2003-06-23 23:39 ` Andries Brouwer
2003-06-24  0:31   ` Frank Cusack
2003-06-24  8:14     ` Andries Brouwer
2003-06-24  3:45   ` H. Peter Anvin
2003-06-24  4:22     ` Werner Almesberger
2003-06-24  4:27       ` H. Peter Anvin
2003-06-24 11:13         ` Werner Almesberger
2003-06-24 15:29           ` H. Peter Anvin [this message]
2003-06-24 15:42             ` John Coffman

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=3EF86E50.20504@zytor.com \
    --to=hpa@zytor.com \
    --cc=johninsd@san.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa@almesberger.net \
    /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.