From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/4] Improvements to i.MX6 SABRESD boards support
Date: Mon, 22 Sep 2014 16:41:33 +0200 [thread overview]
Message-ID: <5420351D.9050802@lucaceresoli.net> (raw)
In-Reply-To: <542020B1.60500@lucaceresoli.net>
Hi,
Luca Ceresoli wrote:
> Dear Thomas,
>
> thanks for your suggestions.
>
> Thomas Petazzoni wrote:
>> Dear Luca Ceresoli,
>>
>> On Fri, 19 Sep 2014 16:12:48 +0200, Luca Ceresoli wrote:
>>
>>> Luca Ceresoli (3):
>>> configs/freescale_imx6qsabresd: rename imx6 to imx6q
>>> configs/freescale_imx6dlsabresd: add defconfig for iMX6DL SabreSD
>>> freescale/imx6-sabresd: document how to create a bootable SD
>>>
>>> Vincent Stehl? (1):
>>> imx6sabresd: boot to /init in mfgtools mode
>>
>> I've applied your four patches. However, I'd like to see additional
>> patches to make the following improvements:
>>
>> * For the defconfigs, select a specific version of the kernel headers.
>> Currently, your defconfigs are building a 3.10 kernel, but the
>> kernel headers used in the toolchain are the latest ones (i.e 3.16
>> currently), which is not good. This was already wrong in the
>> existing defconfig, so I applied your patches nonetheless. But it
>> should be fixed.
>
> I'm working on this. I switched from Freescale's git repo to vanilla
> Linux, since the Freescale releases do not provide any later version.
...or maybe I'll do the other way around: use the kernel headers from
Freescale's custom git repo, since the defconfig we currently use
(imx_v7_defconfig) is not available in mainline, and the closest one
in mainline (imx_v6_v7_defconfig) has several differences, and I'd like
to keep things simple and working.
I wonder if there's a good reason to use a mainline kernel instead.
--
Luca
next prev parent reply other threads:[~2014-09-22 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 14:12 [Buildroot] [PATCH v4 0/4] Improvements to i.MX6 SABRESD boards support Luca Ceresoli
2014-09-19 14:12 ` [Buildroot] [PATCH v4 1/4] configs/freescale_imx6qsabresd: rename imx6 to imx6q Luca Ceresoli
2014-09-19 14:12 ` [Buildroot] [PATCH v4 2/4] configs/freescale_imx6dlsabresd: add defconfig for iMX6DL SabreSD Luca Ceresoli
2014-09-19 14:12 ` [Buildroot] [PATCH v4 3/4] freescale/imx6-sabresd: document how to create a bootable SD Luca Ceresoli
2014-09-19 14:12 ` [Buildroot] [PATCH v4 4/4] imx6sabresd: boot to /init in mfgtools mode Luca Ceresoli
2014-09-21 19:25 ` [Buildroot] [PATCH v4 0/4] Improvements to i.MX6 SABRESD boards support Thomas Petazzoni
2014-09-22 13:14 ` Luca Ceresoli
2014-09-22 14:41 ` Luca Ceresoli [this message]
2014-09-22 15:08 ` Thomas Petazzoni
2014-09-22 13:31 ` Luca Ceresoli
2014-09-22 13:33 ` Thomas Petazzoni
2014-09-22 14:45 ` Luca Ceresoli
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=5420351D.9050802@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.