From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 4/9] board / intel: Add SPI peripherals for Minnowboard MAX
Date: Thu, 25 Aug 2016 23:47:15 +0200 [thread overview]
Message-ID: <20160825234715.1e500fc5@free-electrons.com> (raw)
In-Reply-To: <1472133887-34746-5-git-send-email-andriy.shevchenko@linux.intel.com>
Hello,
On Thu, 25 Aug 2016 17:04:42 +0300, Andy Shevchenko wrote:
> From: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Add two SPI peripherals which can be connected to Minnowboard MAX low speed
> connector. First is Atmel AT25 compatible SPI EEPROM and second is M25P80
> compatible SPI serial flash.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> board/intel/minnowboard-max/acpi/at25.asl | 58 +++++++++++++++++++++++++++++
> board/intel/minnowboard-max/acpi/m25p80.asl | 52 ++++++++++++++++++++++++++
> 2 files changed, 110 insertions(+)
> create mode 100644 board/intel/minnowboard-max/acpi/at25.asl
> create mode 100644 board/intel/minnowboard-max/acpi/m25p80.asl
Is there some upstream project for those ACPI tables? I wouldn't want
to have them all in Buildroot, I'd very much prefer to have a Buildroot
package download them, compile them using the acpica compiler, and
install them in the proper place.
It's fine to have them in Buildroot as a temporary solution, as long as
some upstream is being put in place. But if the long term idea is to
keep those ACPI tables source code in Buildroot, then I don't think
it's what we want to do.
This of course applies to patches 4/9 to 9/9.
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-25 21:47 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
[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 [this message]
[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=20160825234715.1e500fc5@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