From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs/arcturus_ucp1020_defconfig
Date: Thu, 13 Jul 2017 19:21:07 +0200 [thread overview]
Message-ID: <20170713192107.3d951b53@windsurf.lan> (raw)
In-Reply-To: <d52a1493-e225-d781-71f8-97af8212ba77@arcturusnetworks.com>
Hello,
On Thu, 13 Jul 2017 12:20:54 -0400, Oleksandr G Zhadan wrote:
> Looks like we mixed two architectures:
>
> We have arcturus_ucp1020_defconfig (board/arcturus/ppc-ucp1020) already
> in buildroot tree for a while and we been using public kernel with our
> patches.
> Recently I tested the build of it and found that with latest GCC-6 we
> have an issue to build image for this existing board (uCP1020), but it
> was building OK when the latest was GCC-4.9. I agree with you that it
> is better to port GCC-6 issue fix and use GCC-6, I already tested it
> here and will added that linux-3.18 patch into my board patch directory.
> The updated patch for uCP1020 I will send soon.
>
> The arcturus_ucls1012a_defconfig (board/arcturus/aarch64-ucls1012a) is
> another board support package we are trying to add to buildroot now.
> And in patches for this board we are using
> "BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="https://www.arcturusnetworks.com/OSS/kernel-ucls1012a-170706-13.tar.gz".
> The v4 of the patch for uCLS1012a is waiting for your approval.
Indeed, I got confused by the two defconfigs. Thanks for clarifying the
situation!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-13 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 18:31 [Buildroot] [PATCH 1/1] configs/arcturus_ucp1020_defconfig Oleksandr Zhadan
2017-07-13 7:42 ` Thomas Petazzoni
2017-07-13 13:31 ` Oleksandr G Zhadan
2017-07-13 13:38 ` Thomas Petazzoni
2017-07-13 14:14 ` Oleksandr G Zhadan
2017-07-13 15:33 ` Thomas Petazzoni
2017-07-13 16:20 ` Oleksandr G Zhadan
2017-07-13 17:21 ` Thomas Petazzoni [this message]
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=20170713192107.3d951b53@windsurf.lan \
--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