From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, SYSLINUX@zytor.com
Subject: Re: [PATCH] /proc/sys/kernel/bootloader_type
Date: Fri, 31 Dec 2004 12:10:47 -0800 [thread overview]
Message-ID: <41D5B247.1080700@zytor.com> (raw)
In-Reply-To: <20041231013443.313a3320.akpm@osdl.org>
Andrew Morton wrote:
> "H. Peter Anvin" <hpa@zytor.com> wrote:
>
>>This patch exports to userspace the boot loader ID which has been
>> exported by (b)zImage boot loaders since boot protocol version 2.
>
> Why does userspace need to know this?
>
In order to try to figure out what the boot medium was. For some boot
loaders, like grub, it could be more or less anything, but others, e.g.
syslinux, knowing what the boot loader is lets you know what the medium was.
>
>> --- linux-2.5/arch/i386/Makefile 24 Dec 2004 21:09:54 -0000 1.73
>> +++ linux-2.5/arch/i386/Makefile 28 Dec 2004 04:56:17 -0000
>> @@ -20,6 +20,10 @@
>> LDFLAGS_vmlinux :=
>> CHECKFLAGS += -D__i386__
>>
>> +# This allows compilation with an x86-64 compiler
>> +CC_M32 := $(call cc-option,-m32)
>> +CC += $(CC_M32)
>
>
> Was this hunk deliberately a part of this patch?
No, that was a separate patch I submitted several weeks ago which was
apparently still in that tree. Would be good to get that patch into the
tree, though; it allows an x86-64 setup to compile an i386 kernel with
only make ARCH=i386.
-hpa
next prev parent reply other threads:[~2004-12-31 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:39 [PATCH] /proc/sys/kernel/bootloader_type H. Peter Anvin
2004-12-31 9:34 ` Andrew Morton
2004-12-31 10:12 ` Arjan van de Ven
2004-12-31 14:24 ` Coywolf Qi Hunt
2004-12-31 14:36 ` Arjan van de Ven
2004-12-31 20:10 ` H. Peter Anvin [this message]
2005-01-01 20:22 ` Kay Sievers
2005-01-02 8:56 ` Lethalman
-- strict thread matches above, loose matches on Subject: below --
2005-01-01 9:39 Lethalman
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=41D5B247.1080700@zytor.com \
--to=hpa@zytor.com \
--cc=SYSLINUX@zytor.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox