All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Drolez <ldrolez@linbox.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Broken A20 gate handling (about GPL)
Date: Fri, 01 Jul 2005 19:01:32 +0200	[thread overview]
Message-ID: <42C576EC.1090908@linbox.com> (raw)
In-Reply-To: <200507011816.51627.okuji@enbug.org>

Yoshinori K. Okuji wrote:
> In the case of the A20, I'm not sure how I want to implement it. It is not 
> that bad to use syslinux code, because we have our own alternative. However, 
> this code is very critical, and I prefer writing our own code. After all, my 
> opinion looks like the same as Marco. :p

Yes this code is critical, as you see flaws in this code makes grub unusable on 
new PCs (freeze without *any* error message). Since it's the most critical part 
of grub, why simply not use the most stable code available for A20 handling: the 
linux kernel ?

Moreover, IMHO, it makes no sense trying to rewrite such low level functions, 
since there are not hundreds ways of writing it !

Cheers,

-- 
Ludovic DROLEZ



  reply	other threads:[~2005-07-01 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 15:33 Broken A20 gate handling Ludovic Drolez
2005-07-01  9:08 ` Ludovic Drolez
2005-07-01 10:35   ` Marco Gerards
2005-07-01 12:43     ` Broken A20 gate handling (about GPL) Ludovic Drolez
2005-07-01 16:13       ` Hollis Blanchard
2005-07-01 16:16       ` Yoshinori K. Okuji
2005-07-01 17:01         ` Ludovic Drolez [this message]
2005-07-01 17:21           ` Yoshinori K. Okuji
2005-07-01 17:43           ` [Bulk] Re: Broken A20 gate handling (about GPL & FSF copyright assignment) Vincent Pelletier
2005-07-04 13:13         ` Broken A20 gate handling (about GPL) Marco Gerards
2005-07-01 13:54     ` Broken A20 gate handling Ludovic Drolez
2005-07-01 21:21     ` Peter Jones

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=42C576EC.1090908@linbox.com \
    --to=ldrolez@linbox.com \
    --cc=grub-devel@gnu.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.