From: William Lee Irwin III <wli@holomorphy.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Lincoln D. Durey" <durey@EmperorLinux.com>,
LKML <linux-kernel@vger.kernel.org>,
David Hinds <dhinds@sonic.net>,
Emperor Research <research@EmperorLinux.com>
Subject: Re: Sony S170 + 1GB ram => Yenta: ISA IRQ mask 0x0000
Date: Tue, 26 Oct 2004 17:08:27 -0700 [thread overview]
Message-ID: <20041027000827.GL15367@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410261641480.28839@ppc970.osdl.org>
On Tue, 26 Oct 2004, Lincoln D. Durey wrote:
>> well, it must be the boot loader, as the kernel didn't add that, and we
>> didn't ... looking at the GRUB source ... ARGH: we see in stage2/boot.c in
>> that big comment about boot proto 2.03 that grub is indeed adding kernel
>> command line options, (even to 2.4.24 and 2.6.8). How can this be? Their
>> code says it shouldn't, but it does.
On Tue, Oct 26, 2004 at 04:44:36PM -0700, Linus Torvalds wrote:
> Ok, good to know that the kernel was correct, but it might be worthwhile
> trying to debug why grub thinks it should do it's (incorrect) memory map.
> Also, I'd suggest somebody send the grub team a patch to remove the whole
> damn mess, I doubt anybody who installs a new bootloader is interested in
> installing a buggy one.
> Pretty much every kernel has done a better job of memory sizing than grub
> seems to do, and I suspect even the "pre-2.4.14" case was just a total bug
> in grub, and nothing else.
The grub mem= is a major screwup. It's worse than that, though. grub
also hardcodes MAXMEM, which it should obtain from the bzImage.
-- wli
prev parent reply other threads:[~2004-10-27 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:42 Sony S170 + 1GB ram => Yenta: ISA IRQ mask 0x0000 Lincoln D. Durey
2004-10-26 18:28 ` Linus Torvalds
2004-10-26 21:58 ` David Hinds
2004-10-26 23:18 ` Lincoln D. Durey
2004-10-26 23:44 ` Linus Torvalds
2004-10-27 0:08 ` William Lee Irwin III [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=20041027000827.GL15367@holomorphy.com \
--to=wli@holomorphy.com \
--cc=dhinds@sonic.net \
--cc=durey@EmperorLinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=research@EmperorLinux.com \
--cc=torvalds@osdl.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.