From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Dave Jones <davej@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: boot option for CONFIG_EDD_SKIP_MBR?
Date: Thu, 04 Nov 2004 15:49:02 +0100 [thread overview]
Message-ID: <418A415E.40104@gmx.net> (raw)
In-Reply-To: <20041104141233.GA32342@redhat.com>
Dave Jones schrieb:
> On Thu, Nov 04, 2004 at 07:45:34AM -0600, Matt Domsch wrote:
> > On Thu, Nov 04, 2004 at 02:35:58PM +0100, Carl-Daniel Hailfinger wrote:
> > > [please CC: me on replies]
> > > having had problems (inifinte hang on boot) with some Fujitsu
> > > Siemens Scenic computers when EDD was enabled, I asked myself
> > > if it would be possible to add a boot option edd=nombr and
> > > possibly also another boot option edd=off to the EDD code in
> > > the kernel. These would correspond to CONFIG_EDD_SKIP_MBR
> > > and CONFIG_EDD, respectively.
> > >
> > > Yes, option parsing before entering protected mode is ugly,
> > > but the vga setup code does it, too.
> > >
> > > What do you think?
> >
> > I'd love it. I hadn't done it as I thought it would be ugly, and so
> > far I could blame buggy BIOSes for the delay. If you want to work up
> > a patch, I'll gladly review and apply something that does such.
>
> But would this actually be useful for the cases where EDD has been
> broken so far ? AFAIR, the bootparam parsing happens /after/
> we do the 16-bit EDD asm foo.
AFAIR the VGA setup code does its bootparam parsing by hand because it
suffers from the same problem.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
prev parent reply other threads:[~2004-11-04 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 13:35 boot option for CONFIG_EDD_SKIP_MBR? Carl-Daniel Hailfinger
2004-11-04 13:45 ` Matt Domsch
2004-11-04 14:12 ` Dave Jones
2004-11-04 14:49 ` Carl-Daniel Hailfinger [this message]
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=418A415E.40104@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=Matt_Domsch@dell.com \
--cc=davej@redhat.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