From: Bernhard Walle <bwalle@suse.de>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] Update 32 bit boot protocol
Date: Wed, 21 May 2008 13:29:28 +0200 [thread overview]
Message-ID: <20080521132928.29df44e5@halley.suse.de> (raw)
In-Reply-To: <20080521061225.GG3714@verge.net.au>
* Simon Horman [2008-05-21 16:12]:
>
> On Fri, May 09, 2008 at 06:43:55PM +0200, Bernhard Walle wrote:
> > This patch updates the boot protocol to match with the kernel. See
> > Documentation/i386/zero-page.txt in kernel.
> >
> > The number of E820 map entries have been increased from 32 to 128. The update
> > is necessary for the next patch that implements EDD support for kexec.
> > when using the default 32 bit mode.
> >
> >
> > Signed-off-by: Bernhard Walle <bwalle@suse.de>
>
> Thanks, I have applied this change, though I
> am a little confused about the relationship between
> the information in (kernel/)Documentation/i386/zero-page.txt and
> (kexec-tools-testing/)doc/linux-i386-zero-page.txt.
Well, it's supposed to contain the same information. I think the 32 bit
boot protocol, i.e. the communication between the "setup" part of
bzImage and the real Linux kernel, was "explored" and used by kexec
first and then "standardised" by Linux developers. Therefore, the
documentation appeared first in kexec-tools and then some kernel
developer put it into documentation tree of the kernel.
Maybe it would make also sense to remove that part of documentation
from kexec and just refer to the (more up to date) Linux documentation.
But I leave this up to your decision. I just discovered that mistake.
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2008-05-21 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:43 [PATCH] Update 32 bit boot protocol Bernhard Walle
2008-05-21 6:12 ` Simon Horman
2008-05-21 11:29 ` Bernhard Walle [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=20080521132928.29df44e5@halley.suse.de \
--to=bwalle@suse.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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