From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [RFC] platform: update galileo to 3.14 kernel
Date: Mon, 29 Aug 2016 13:19:59 +0200 [thread overview]
Message-ID: <20160829131959.09cf41e3@free-electrons.com> (raw)
In-Reply-To: <E704BB48EC9FDF4FA0A7A278C2546ACFE27080@irsmsx105.ger.corp.intel.com>
Hello,
On Mon, 29 Aug 2016 10:20:18 +0000, Connolly, Padraig wrote:
> Currently there is support for the Quark X1000 SoC itself in the upstream Linux Kernel
> but support for the Galileo Gen 1/2 is not fully upstream, there is a Galileo platform driver that is not upstream.
> There is also some fixes that affect the USB behavior that are not upstream either.
>
> This means anything supported by the platform driver will not work with the upstream kernel,
> for example GPIO, I2C, and SPI. USB device support is also less reliable without the fix.
>
> You can find the platform driver in our GitHub repo here :
> https://github.com/padraigconnolly/Linux-x1000/tree/master/drivers/platform/x86/intel-quark
Then, it's fine to use a non-upstream kernel for this platform. Just
update the existing galileo_defconfig.
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-29 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:25 [Buildroot] [PATCH] [RFC] platform: update galileo to 3.14 kernel Padraig James Connolly
2016-08-22 12:46 ` Andy Shevchenko
2016-08-22 12:54 ` Andy Shevchenko
2016-08-22 13:54 ` Connolly, Padraig
2016-08-22 14:33 ` Thomas Petazzoni
2016-08-23 8:05 ` Connolly, Padraig
2016-08-23 9:25 ` Thomas Petazzoni
2016-08-29 10:20 ` Connolly, Padraig
2016-08-29 11:15 ` Kinsella, Ray
2016-08-29 11:19 ` Thomas Petazzoni [this message]
2016-08-29 12:32 ` Connolly, Padraig
2016-08-29 12:48 ` Andy Shevchenko
2016-08-29 13:14 ` Kinsella, Ray
2016-08-29 13:52 ` 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=20160829131959.09cf41e3@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