From: "Vincent Stehlé" <vincent.stehle@freescale.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: add defconfig for Freescale i.MX31 PDK
Date: Thu, 19 Mar 2015 16:37:35 +0100 [thread overview]
Message-ID: <550AED3F.4070606@freescale.com> (raw)
In-Reply-To: <550A0AF9.5050101@mind.be>
On 03/19/2015 12:32 AM, Arnout Vandecappelle wrote:
..
> Doesn't the upstream MACH_MX31_3DS work? 2.6.28 is extremely old...
Hi Arnout,
Thank you for reviewing this patch so quickly and sending
feedbacks.
This defconfig is indeed based on an old 2.6.28 kernel; the idea
was to base the defconfig on the last Freescale "official"
release, which works fine for me.
You are right that mainline kernel has support for the i.MX31
processor, but there is no dts in there for the i.MX31 PDK right
now. The few tries I just did do not boot "as is" but I will
continue a bit.
Do you insist that this i.MX31 config uses mainline, or would
it be acceptable to stay on the "old", Freescale "official"
kernel?
..
>> +BR2_KERNEL_HEADERS_3_2=y
> That doesn't sound like a good idea when the kernel is 2.6.28...
Granted, this is not optimal. Those are the kernel headers
closest to 2.6.28, "easily" available in buildroot.
It is indeed possible to manually specify the 2.6.28 kernel
headers version, but this necessitates two patches to fix the
linux-headers "build".
Do you prefer this solution?
..
>> +BR2_TOOLCHAIN_BUILDROOT_EGLIBC=y
>> +BR2_TOOLCHAIN_BUILDROOT_CXX=y
> Why not uClibc and why C++?
Those are "leftovers", sorry. Thanks for spotting those mistakes.
I will remove that.
..
>> +BR2_ROOTFS_DEVICE_CREATION_STATIC=y
> With a more recent kernel we don't need this crappy option...
This is correct: this is necessary only with the "official"
release kernel.
..
>> +# BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
> Why?
Also "leftovers", sorry. Thanks for spotting, I will remove as
well.
..
> If network boot is really the only option, then perhaps it would be nicer to
> use an initramfs linked into the kernel? Or doesn't the board have enough memory
> to support that?
This is my only boot method for the moment.
Do you insist that the defconfig should use MMC?
I will continue to try a bit to generate a suitable MMC with
buildroot anyway. Maybe that can be changed in the defconfig later
on?
On the other hand, if we stay with network booting, initramfs is
a nice idea as it makes the setup simpler indeed. Also, the
i.MX31 PDK has 128 MB of memory, so this is a practical solution.
I just tested and an initramfs included in the zImage works
fine. Only, Freescale "official" kernel has no support for
initrd/initramfs, so we need another patch.
Would you prefer this solution?
I will send a v2 patch right away, with a few reworks discussed
here, and still based on the "old" Freescale "official" release.
Please let me know if this is going in the right direction (or
not ;)
Thanks again for reviewing!
Best regards,
V.
next prev parent reply other threads:[~2015-03-19 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 9:43 [Buildroot] [PATCH] configs: add defconfig for Freescale i.MX31 PDK Vincent Stehlé
2015-03-18 23:32 ` Arnout Vandecappelle
2015-03-19 15:37 ` Vincent Stehlé [this message]
2015-03-19 15:58 ` Thomas Petazzoni
2015-03-19 21:26 ` Arnout Vandecappelle
2015-03-19 21:28 ` Arnout Vandecappelle
2015-03-20 14:53 ` Vincent Stehlé
2015-03-20 14:57 ` [Buildroot] [PATCH v4] " Vincent Stehlé
2015-03-21 17:27 ` Arnout Vandecappelle
2015-03-24 18:51 ` Vincent Stehlé
2015-03-24 18:53 ` [Buildroot] [PATCH v5] " Vincent Stehlé
2015-03-25 0:02 ` Thomas Petazzoni
2015-03-19 15:52 ` [Buildroot] [PATCH v2] " Vincent Stehlé
2015-03-19 21:32 ` Arnout Vandecappelle
2015-03-20 9:02 ` Vincent Stehlé
2015-03-20 9:05 ` [Buildroot] [PATCH v3] " Vincent Stehlé
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=550AED3F.4070606@freescale.com \
--to=vincent.stehle@freescale.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 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.