From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ext-toolchain-wrapper issues
Date: Sat, 4 Aug 2012 18:58:14 +0200 [thread overview]
Message-ID: <20120804185814.3c51db5c@skate> (raw)
In-Reply-To: <CAE9DZUROhjmKaqYqPoYPa0gy2RhxnX0dvQ4+XJ+2Z2nwjQed+w@mail.gmail.com>
Hello,
Le Sat, 4 Aug 2012 11:25:40 -0500,
Dallas Clement <dallas.a.clement@gmail.com> a ?crit :
> > Interesting, I'm also working around the Armada 370 and Armada XP.
> > What are you doing with this platform?
>
> Building a NAS product.
>
> > The Armada XP support in mainline doesn't need machine type, it uses
> > the device tree.
>
> Marvell provides a patch to the 3.0.6 kernel, which definitely
> provides machine types. They have 3 or 4 defconfigs for the Armada
> XP.
Ok. We are currently mainlining support for the Armada XP, but it's far
from being complete enough to build a NAS product right now.
> > Is this Marvell toolchain available somewhere so I can try to
> > reproduce the problem?
>
> You have to get it from Marvell's extranet. Need to register first.
> Pls contact Erez who is the FAE if you need help getting in
> (ereza at marvell.com).
Ok, then I will not be able to do this right now. I am behind a 3G
connection during my holidays, so I will not do a full toolchain
download.
> I'll do that. It would be nice to get it figured out. Will let you
> know what I find.
Yes, that would be good, thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-08-04 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 17:21 [Buildroot] ext-toolchain-wrapper issues Dallas Clement
2012-08-04 9:19 ` Thomas Petazzoni
2012-08-04 16:25 ` Dallas Clement
2012-08-04 16:58 ` Thomas Petazzoni [this message]
2012-08-08 16:12 ` Dallas Clement
2012-08-08 19:07 ` Thomas Petazzoni
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=20120804185814.3c51db5c@skate \
--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.