From: Robert Millan <rmh@aybabtu.com>
To: okuji@enbug.org
Cc: grub-devel@gnu.org
Subject: buggy BIOSes (Re: pretty colors in gfxterm)
Date: Fri, 31 Aug 2007 16:47:14 +0200 [thread overview]
Message-ID: <20070831144714.GB28075@thorin> (raw)
In-Reply-To: <20070831144219.GA27818@thorin>
> Besides that, it is really necessary to check what workarounds for buggy
> BIOSes are missing in GRUB 2. The current bootstrap code on PC is based on
> somewhere around GRUB 0.96, so it is a bit outdated.
I just had a look. Is there something other than:
2005-03-15 Yoshinori K. Okuji <okuji@enbug.org>
* stage2/fsys_fat.c (fat_mount): Ignore the 3rd bit of a media
descriptor, because some BIOSes overwrite this value, according
to the storage mode (e.g. USB Floppy or USB HDD).
[...]
2005-02-15 Yoshinori K. Okuji <okuji@enbug.org>
* stage2/builtins.c (install_func): If DEST_DRIVE is a hard
disk, enable the workaround in Stage 1 by replacing the jmp
with double nop's.
* stage1/stage1.h (STAGE1_BOOT_DRIVE_CHECK): New macro.
(STAGE1_BOOT_DRIVE_MASK): Removed.
* stage1/stage1.S (boot_drive_check): New label. This implements
a different workaround for buggy BIOSes which don't pass boot
drive correctly. This is effective for BIOSes which pass a value
without the seventh bit (0x80).
(boot_drive_mask): Removed.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next parent reply other threads:[~2007-08-31 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070831144219.GA27818@thorin>
2007-08-31 14:47 ` Robert Millan [this message]
2007-09-02 10:02 ` buggy BIOSes (Re: pretty colors in gfxterm) Yoshinori K. Okuji
2007-09-02 10:52 ` Robert Millan
2007-09-03 19:46 ` Yoshinori K. Okuji
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=20070831144714.GB28075@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=okuji@enbug.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.