From: "H. Peter Anvin" <hpa@zytor.com>
To: trenn@suse.de
Cc: Richard <tuxbox.guru@gmail.com>,
linux-acpi@vger.kernel.org, "Langsdorf,
Mark" <mark.langsdorf@amd.com>,
andreas.herrmann3@amd.com
Subject: Overriding ACPI tables
Date: Wed, 30 Apr 2008 10:56:33 -0700 [thread overview]
Message-ID: <4818B2D1.30209@zytor.com> (raw)
In-Reply-To: <1209544792.29352.78.camel@linux-2bdv.site>
Thomas Renninger wrote:
> Peter: You wrote the syslinux stuff, right? What kind of luck is that :)
> There currently is a discussion about being able to override ACPI tables
> via initrd. The discussion is a bit stuck because the data is needed
> earlier than initrd is unpacked and the hacks to make it work are not
> accepted by Linus. I thought about adding another binary image to i386
> boot protocol, similar to initrd= which contains data for very early
> kernel boot initialization, but this would be a heavy hammer (but IMO
> still better than only do it for kexec, another suggestion...) , I
> better open a separate thread or pre-ask privately whether this makes
> sense at all. It would be great if you could advise and possibly help to
> convince so that we finally may find a solution accepted mainline.
We're putting in a mechanism for pushing larger tables already; we need
it for other things (in particular, the zones for E820 and EDD in the
boot_info_table are simply not big enough.) That gives a generic
mechanism for sending arbitrary-sized binary images to the kernel. That
would be the mechanism to use.
I believe it's in upstream as this merge window; it's definitely in
x86.git already.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-04-30 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 9:06 ACPI on Compaq 6715b - BIOS from the wrong end of the planet Richard
2008-04-29 13:45 ` Thomas Renninger
2008-04-29 15:57 ` Richard
2008-04-29 18:29 ` Thomas Renninger
2008-04-29 23:36 ` H. Peter Anvin
2008-04-30 8:30 ` Richard
2008-04-30 8:39 ` Thomas Renninger
2008-04-30 10:23 ` Richard
2008-04-30 12:07 ` Thomas Renninger
2008-04-30 13:09 ` Richard
2008-04-30 13:34 ` Richard
2008-04-30 13:58 ` Thomas Renninger
2008-04-30 17:56 ` H. Peter Anvin [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=4818B2D1.30209@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.herrmann3@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=trenn@suse.de \
--cc=tuxbox.guru@gmail.com \
/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