From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building system for the Marvell's ARMADA A385 borad to resolve the VLAN trunk issue
Date: Thu, 24 Sep 2015 23:48:12 +0200 [thread overview]
Message-ID: <871tdno5er.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150923170613.75f5e7e4@free-electrons.com> (Thomas Petazzoni's message of "Wed, 23 Sep 2015 17:06:13 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> The reason why I didn't submit a defconfig is because there is no
> full-featured publicly available bootloader for these platforms. The
> bootloader provided by Marvell is not publicly available (you have to
> be a customer, and use an account to access their Extranet and download
> the U-Boot sources). There is now some U-Boot support in the mainline
> U-Boot, but I haven't tried it yet.
Ok, but I guess missing open u-boot support shouldn't be a deal
breaker. We already have a few defconfigs without bootloader config
(lego_ev3, openblocks_a6, s6lx9_microboard, ..).
> So I could submit a huge bunch of defconfigs for all the Armada 370,
> XP, 375, 38x and 39x platforms that I have (it would probably be 15 to
> 20 defconfigs), but they would only differ by the name of the Device
> Tree in the defconfig. All the rest would be exactly the same. So I
> wasn't sure it was really worth adding 15 to 20 more defconfigs for a
> configuration that doesn't include the bootloader and where all
> configurations would be almost identical.
Couldn't we just do a single defconfig that builds all the dtb files and
then add a README describing what dtb / how to boot on the various
boards?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-09-24 21:48 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
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 [this message]
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=871tdno5er.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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