From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] freescale_imx31_3stack_defconfig fails to build
Date: Sat, 5 Nov 2016 16:26:38 +0100 [thread overview]
Message-ID: <20161105162638.6a268cbc@free-electrons.com> (raw)
In-Reply-To: <CAOMZO5Dv5=_x2y-_WtgW3G2Ox8TQpREwJkGhOx5cK5Fpk5uxfg@mail.gmail.com>
Hello,
On Sat, 5 Nov 2016 13:05:43 -0200, Fabio Estevam wrote:
> > Has one of you access to this platform, and be willing to update this
> > defconfig?
>
> I think we should be able to use the latest mainline on mx31pdk.
>
> I will try to get access to a mx31pdk and will give it a try with
> latest mainline.
Great, thanks!
Bonus point for other improvements to the defconfig, such as adding the
build for the bootloader, etc :)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-05 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 13:35 [Buildroot] freescale_imx31_3stack_defconfig fails to build Thomas Petazzoni
2016-11-05 15:05 ` Fabio Estevam
2016-11-05 15:26 ` Thomas Petazzoni [this message]
2016-11-05 15:27 ` Fabio Estevam
[not found] ` <6234984d-6409-37c1-b050-504775d37c17@bergerie>
2016-11-05 16:16 ` Thomas Petazzoni
2016-11-05 16:37 ` Fabio Estevam
2016-11-08 20:41 ` [Buildroot] [PATCH] configs: freescale_imx31_3stack: bump kernel version to 4.1.15_2.0.0_ga Vincent Stehle
2016-11-09 16:38 ` Vincent Stehle
2016-11-09 20:32 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2018-03-04 21:55 [Buildroot] freescale_imx31_3stack_defconfig fails to build Thomas Petazzoni
2018-03-04 23:21 ` Fabio Estevam
2018-03-05 7:53 ` Thomas Petazzoni
2018-03-05 11:03 ` Fabio Estevam
2018-03-10 14:40 ` Fabio Estevam
2018-03-10 15:39 ` Fabio Estevam
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=20161105162638.6a268cbc@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 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.