From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 3/9] board/intel/common: Add possibility for adding ACPI tables to the initrd
Date: Fri, 26 Aug 2016 11:30:22 +0200 [thread overview]
Message-ID: <20160826113022.2748b435@free-electrons.com> (raw)
In-Reply-To: <20160826090454.GK1812@lahna.fi.intel.com>
Hello,
On Fri, 26 Aug 2016 12:04:54 +0300, Mika Westerberg wrote:
> > On 25-08-16 16:04, Andy Shevchenko wrote:
> > > Add script which takes ASL files as input, compiles them to AML bytecode,
> > > and prepends the whole thing to the initrd archive. They are placed in
> > > kernel/firmware/acpi directory where the kernel is able to find and use
> > > them.
> >
> > Why is this a post-image script, and not just a post-build script that copies
> > everything in the right place and lets the cpio rootfs take care of generating
> > the cpio? AFAIK there is no particular requirement for this stuff to be at the
> > beginning of the cpio image, is there?
>
> Actually there is - the kernel looks only from the first uncompressed
> cpio archive for these additional AML files.
Still not clear: Arnout doesn't suggest to generate multiple cpio
archives, but rather to simply have the AML files within the cpio
archive in the first place.
The Buildroot process looks like this:
1. Build all packages
2. Run post-build scripts
3. Create filesystem images (including cpio one)
4. Run post-image scripts
Right now, if I understand correctly, in step (4), you're generating an
additional initrd with just the AML files. Is this correct?
What about instead having things done in step (2): install the AML
files at the appropriate places in $(TARGET_DIR) so that they
automatically end up in the rootfs.cpio generated by Buildroot?
In this case, there's a single initrd, which contains both the root
filesystem itself and the AML files.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-26 9:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 14:04 [Buildroot] [PATCH v1 0/9] board: introduce common infrastructure for Intel SoCs Andy Shevchenko
2016-08-25 14:04 ` [Buildroot] [PATCH v1 1/9] package/acpica: Add host configuration to the tool Andy Shevchenko
2016-08-25 21:44 ` Thomas Petazzoni
2016-08-26 10:50 ` Erico Nunes
2016-08-25 14:04 ` [Buildroot] [PATCH v1 2/9] board/intel/common: Add common files for x86 boards Andy Shevchenko
2016-08-25 21:37 ` Thomas Petazzoni
2016-08-26 16:42 ` Arnout Vandecappelle
2016-08-25 14:04 ` [Buildroot] [PATCH v1 3/9] board/intel/common: Add possibility for adding ACPI tables to the initrd Andy Shevchenko
2016-08-25 21:43 ` Thomas Petazzoni
2016-08-26 6:13 ` Arnout Vandecappelle
2016-08-26 8:39 ` Thomas Petazzoni
[not found] ` <20160826090454.GK1812@lahna.fi.intel.com>
2016-08-26 9:30 ` Thomas Petazzoni [this message]
[not found] ` <20160826093901.GO1812@lahna.fi.intel.com>
2016-08-26 13:28 ` Thomas Petazzoni
2016-08-26 16:30 ` Arnout Vandecappelle
[not found] ` <20160829065522.GV1812@lahna.fi.intel.com>
2016-08-29 7:45 ` Arnout Vandecappelle
[not found] ` <20160829075810.GA1709@lahna.fi.intel.com>
2016-08-29 9:08 ` Arnout Vandecappelle
2016-08-25 14:04 ` [Buildroot] [PATCH v1 4/9] board / intel: Add SPI peripherals for Minnowboard MAX Andy Shevchenko
2016-08-25 21:47 ` Thomas Petazzoni
[not found] ` <20160826090917.GL1812@lahna.fi.intel.com>
2016-08-26 9:26 ` Thomas Petazzoni
2016-08-25 14:04 ` [Buildroot] [PATCH v1 5/9] board / intel: Add SPI peripherals for Joule Andy Shevchenko
2016-08-25 14:04 ` [Buildroot] [PATCH v1 6/9] board / intel: Add Aosong AM2315 sensor for Intel Joule Andy Shevchenko
2016-08-25 14:04 ` [Buildroot] [PATCH v1 7/9] board / intel: Add GPIO LEDs " Andy Shevchenko
2016-08-25 14:04 ` [Buildroot] [PATCH v1 8/9] board / intel: Add GPIO LEDs for Intel Minnowboard Andy Shevchenko
2016-08-25 14:04 ` [Buildroot] [PATCH v1 9/9] board / intel: Add GPIO buttons " Andy Shevchenko
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=20160826113022.2748b435@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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