All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Drolez <ldrolez@linbox.com>
To: grub-devel@gnu.org
Subject: Broken A20 gate handling
Date: Thu, 30 Jun 2005 17:33:02 +0200	[thread overview]
Message-ID: <42C410AE.1030707@linbox.com> (raw)

Hi !

Recently I tried to use grub(2) with a compaq evo D510. These boxes do not seem 
to have a keyboard controller, so grub freeze in gatea20().

Most free bootloaders fail, but one is okay: syslinux/isolinux.

I've taken a look at syslinux's code, and indeed A20 activation is done much 
more carefully than in grub, and more tricks are used.

I think it's really important to fix grub's code (by stealing code from isolinux 
?), because more and more PCs without a good old keyboard controller will hit 
the market.

Are there any plans to improve gatea20() ? (Moreover, grub2's code for gatea20 
is even worse than grub-legacy)

Regards,

-- 
Ludovic DROLEZ



             reply	other threads:[~2005-06-30 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 15:33 Ludovic Drolez [this message]
2005-07-01  9:08 ` Broken A20 gate handling 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
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=42C410AE.1030707@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.