From: "Pascal Bellard" <pascal.bellard@ads-lu.com>
To: "Frank Sorenson" <frank@tuxrocks.com>
Cc: riley@williams.name, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [i386 BOOT CODE] kernel bootable again
Date: Wed, 14 Sep 2005 11:52:07 +0200 (CEST) [thread overview]
Message-ID: <33300.85.68.36.53.1126691527.squirrel@212.11.36.192> (raw)
In-Reply-To: <432722A1.8030302@tuxrocks.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Frank,
I have built a new patch based on linux-2.6.13-git12 to avoid build.c
conflict.
Regards,
-pascal
> Pascal Bellard wrote:
>> Hello,
>>
>> Please find attached a patch to build i386/x86_64 kernel directly
>> bootable. It may be usefull for rescue floppies and installation
>> floppies.
>
> Pascal,
>
> In commit f8eeaaf4180334a8e5c3582fe62a5f8176a8c124, build.c has already
> changed, and I don't believe it's very compatible with this change.
>
> See
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f8eeaaf4180334a8e5c3582fe62a5f8176a8c124
>
> Also, we'll need to see comments from H. Peter Anvin on this patch.
> CC'ing him.
[-- Attachment #2: linux-2_6_13-git12-bootblock_u.DEFANGED-14 --]
[-- Type: application/DEFANGED-14, Size: 32124 bytes --]
next prev parent reply other threads:[~2005-09-14 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 13:46 Pascal Bellard
2005-09-13 19:04 ` Frank Sorenson
2005-09-13 19:42 ` H. Peter Anvin
2005-09-14 9:42 ` Pascal Bellard
2005-09-14 9:55 ` Martin Mares
2005-09-14 16:38 ` H. Peter Anvin
2005-09-17 15:26 ` Giuseppe Bilotta
2005-09-17 15:56 ` Jesper Juhl
2005-09-17 16:19 ` Giuseppe Bilotta
2005-09-19 2:13 ` Coywolf Qi Hunt
2005-09-14 9:52 ` Pascal Bellard [this message]
2005-09-20 17:13 Etienne Lorrain
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=33300.85.68.36.53.1126691527.squirrel@212.11.36.192 \
--to=pascal.bellard@ads-lu.com \
--cc=frank@tuxrocks.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riley@williams.name \
/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
all inboxes | Powered by JetHome®