From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86,setup: add serial_console_port_base in boot_params
Date: Sun, 1 Aug 2010 01:31:38 +0400 [thread overview]
Message-ID: <20100731213138.GC29357@lenovo> (raw)
In-Reply-To: <4C548F7D.6000509@zytor.com>
On Sat, Jul 31, 2010 at 02:02:53PM -0700, H. Peter Anvin wrote:
> On 07/31/2010 11:32 AM, Cyrill Gorcunov wrote:
> >>
> >> No, this is the internal part of the boot protocol, so it's not an issue.
> >>
> >
> > Peter, I didn't mean any issue here, I meant that bootloaders don't know about
> > this field yet and they will have to update own sources to pass port value
> > at proper place of boot params. Or I miss something?
> >
>
> Boot loaders that use the 16-bit entry point are unaffected.
>
> Boot loaders which use the 32-bit entry point but properly clears the
> zero page simply will not have the feature.
>
> Boot loaders which use the 32-bit entry point but doesn't clear the zero
> page are broken.
>
> -hpa
>
Well, Peter, seems I messed boot params with setup header. So I don't see
any user of this field then, hmm...
-- Cyrill
next prev parent reply other threads:[~2010-07-31 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 22:27 [PATCH] x86,setup: add serial_console_port_base in boot_params Yinghai Lu
2010-07-16 0:12 ` H. Peter Anvin
2010-07-16 1:30 ` Yinghai Lu
2010-07-31 8:34 ` Cyrill Gorcunov
2010-07-31 18:21 ` H. Peter Anvin
2010-07-31 18:32 ` Cyrill Gorcunov
2010-07-31 21:02 ` H. Peter Anvin
2010-07-31 21:31 ` Cyrill Gorcunov [this message]
2010-08-01 1:53 ` Yinghai Lu
2010-08-01 2:42 ` Eric W. Biederman
2010-08-01 5:20 ` Yinghai Lu
2010-08-03 2:03 ` Eric W. Biederman
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=20100731213138.GC29357@lenovo \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--cc=yinghai@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