[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQVed0tXhbtmc_Gug0gFZ=s=j=N4B5Vr2_ZTmSj6L-65dw@mail.gmail.com>
Date: Wed, 21 Nov 2012 21:56:36 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-kernel@...r.kernel.org, Rob Landley <rob@...dley.net>,
Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH v3 11/12] x86, boot: add fields to support load bzImage
and ramdisk high
On Wed, Nov 21, 2012 at 11:18 AM, H. Peter Anvin <hpa@...or.com> wrote:
> Then whatever loads vmlinux.elf is responsible for initializing those
> fields to zero anyway. It is still an atrocious abuse. What we
> probably need to do is to include the initialized header in a section in
> vmlinux.elf containing the default struct boot_params. This is the kind
> of things that happen when people do things without thinking through all
> the consequences.
ok, will remove the version checking in kernel.
also do you still think need to move ext_ramdisk... ext_cmd_line_ptr
from setup_header to boot_param ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists