From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue
Date: Mon, 21 Sep 2015 21:57:32 +0200 [thread overview]
Message-ID: <5600612C.5060300@mind.be> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474C34B0F@svr-wa-exch1.atg.lc>
On 21-09-15 20:20, Lee, Tommy wrote:
> Hi Buildroot Busybox,
>
>
>
> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I made the former
> meet the latter?s requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9)
> DB-88F6820-GP.
>
>
>
> While resolving my BuidrootLinux-4.0.4 VLAN trunk reachability issue, I
> discovered that Buildroot-2015.05 supports Marvell?s MV78x000 based ARMADA XP
> Family, not the DB-88F6820-GPboard I am currently using.
I think you're confusing buildroot with Linux. Buildroot doesn't have a
defconfig for Armada XP as far as I know.
So you'll have to configure buildroot yourself. Start with selecting
BR2_cortex_a9 for the architecture, configure the toolchain as you like. Then
for the kernel, select an in-tree defconfig and fill in "mvebu_v7" for the
defconfig name. Also select an in-tree device tree and fill in armada-388-gp.
Thomas Petazzoni actually worked on this board I think. Thomas, why didn't you
submit a defconfig? :-P
Regards,
Arnout
>
>
>
> With the current board, I have three approaches to resolve the trunk problem on
> it, from top to bottom:
>
>
>
> 1. Pick ?Marvell MV78xx0?, from the Buildroot-2015.05 ?make
> linux-menuconfig? ARM system type list, for ARMADA A385 to create our .config file.
>
> 2. Upgrade Buildroot-2015.05 to 2015.08 to see whether the ARMADA A38x
> family is included in the ARM system type list.
>
> 3. Get back to buildroot-2012.11-2015_T1.0 which Marvell built their system
> successfully. Follow Marvell?s procedures to build my system.
>
>
>
> I hope you would comment on the above approaches.
>
>
>
> Tommy
>
>
> --------------------------------------------------------------------------------
> This e-mail message is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. Any unauthorized review, use,
> disclosure or distribution is prohibited. If you are not the intended recipient,
> please contact the sender by reply e-mail and destroy all copies of the original
> message. If you are the intended recipient, please be advised that the content
> of this message is subject to access, review and disclosure by the sender's
> e-mail System Administrator.
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-21 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 18:20 [Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue Lee, Tommy
2015-09-21 19:57 ` Arnout Vandecappelle [this message]
2015-09-21 22:28 ` Lee, Tommy
2015-09-21 22:49 ` Arnout Vandecappelle
2015-09-21 23:47 ` Lee, Tommy
2015-09-23 15:06 ` Thomas Petazzoni
2015-09-23 17:58 ` Lee, Tommy
2015-09-24 7:26 ` Thomas Petazzoni
2015-09-24 21:27 ` Lee, Tommy
2015-09-24 0:24 ` Lee, Tommy
2015-09-24 21:48 ` Peter Korsgaard
2015-09-24 22:53 ` Lee, Tommy
2015-09-25 7:39 ` Stefan Peter
2015-09-25 16:07 ` Lee, Tommy
2015-09-25 7:34 ` Thomas Petazzoni
2015-09-25 7:41 ` Peter Korsgaard
2015-09-25 7:53 ` Thomas Petazzoni
2015-09-25 8:57 ` Peter Korsgaard
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=5600612C.5060300@mind.be \
--to=arnout@mind.be \
--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