* [PATCH] remove the warning from arch/i386/boot/setup.S
@ 2004-04-02 17:32 Jörn Engel
0 siblings, 0 replies; only message in thread
From: Jörn Engel @ 2004-04-02 17:32 UTC (permalink / raw)
To: linux-kernel
Not sure how many people tried to fix this before, but it's still in
2.6.4. And guess what, we depend on undocumented behaviour, so I'd
prefer to make this dependency explicit.
Jörn
--
Mundie uses a textbook tactic of manipulation: start with some
reasonable talk, and lead the audience to an unreasonable conclusion.
-- Bruce Perens
The warning is correct, the calculated value for ramdisk_max would be
0xb7ffffff instead of 0x37ffffff. Truncating 0xb7ffffff to 0x37ffffff
is desired behaviour, so we should do it explicitly.
setup.S | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
--- linux-2.6.1/arch/i386/boot/setup.S~initrd_warning 2004-03-09 11:37:29.000000000 +0100
+++ linux-2.6.1/arch/i386/boot/setup.S 2004-03-09 11:38:59.000000000 +0100
@@ -162,7 +162,8 @@
# can be located anywhere in
# low memory 0x10000 or higher.
-ramdisk_max: .long MAXMEM-1 # (Header version 0x0203 or later)
+ramdisk_max: .long (MAXMEM-1) & 0x7fffffff
+ # (Header version 0x0203 or later)
# The highest safe address for
# the contents of an initrd
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-04-02 17:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-02 17:32 [PATCH] remove the warning from arch/i386/boot/setup.S Jörn Engel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®