From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig
Date: Fri, 3 Jan 2020 09:24:43 +0100 [thread overview]
Message-ID: <20200103092443.4e98511a@windsurf> (raw)
In-Reply-To: <BN6PR11MB4145CB3739932D59E074FC1C90200@BN6PR11MB4145.namprd11.prod.outlook.com>
Hello Ray,
On Thu, 2 Jan 2020 21:21:35 +0000
"Kinsella, Ray" <ray.kinsella@intel.com> wrote:
> I had thought about that a few times, upgrading the kernel to the latest and greatest.
>
> A good share of the Quark/X1000 SoC + Galileo Board support was upstreamed to the kernel.
> However some was not.
>
> That out-of-tree 3.14 was the last version Intel engineers validated as supporting all the I/Os etc.
> So there is some unknown delta between the what is supported by the upstream and this out-of-tree kernels
>
> If memory serves me the main difference was the SRAM drivers and some power management features.
>
> Given this board is pretty old.
> I would be inclined to update it to the latest kernel, and we can see if anyone screams.
> No doubt we will be retiring it completely soon enough.
Does it still make sense to have this Galileo defconfig? If I
understood correctly, this platform is no longer sold/supported by
Intel, so perhaps we should simply remove this defconfig, either now or
at some point in the future ?
> You guys heading to FOSDEM this year?
A number of Buildroot developers will indeed be at FOSDEM, since we
organize our Buildroot Developers meeting right after FOSDEM, see
https://elinux.org/Buildroot:DeveloperDaysFOSDEM2020.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-03 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 12:07 [Buildroot] [PATCH] DEVELOPERS: add Nicholas Sielicki as contact for galileo_defconfig Thomas Petazzoni
2019-12-31 15:20 ` Yann E. MORIN
[not found] ` <BN6PR11MB4145284497C2AF782D307B3590260@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01 9:08 ` Yann E. MORIN
[not found] ` <MN2PR11MB4160005AC798211088F160C090210@MN2PR11MB4160.namprd11.prod.outlook.com>
2020-01-01 15:34 ` Thomas Petazzoni
2020-01-01 16:11 ` Yann E. MORIN
[not found] ` <BN6PR11MB4145B63CE33025809CB99F8490210@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-01 21:16 ` Yann E. MORIN
2020-01-02 8:14 ` Thomas Petazzoni
[not found] ` <BN6PR11MB4145CB3739932D59E074FC1C90200@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-03 8:24 ` Thomas Petazzoni [this message]
[not found] ` <BN6PR11MB4145527DD926BC273CA3F6B7903C0@BN6PR11MB4145.namprd11.prod.outlook.com>
2020-01-06 9:42 ` Thomas Petazzoni
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=20200103092443.4e98511a@windsurf \
--to=thomas.petazzoni@bootlin.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