From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for AM3358 AM3359 with wireless-tools shared library
Date: Sun, 28 Oct 2012 10:36:07 +0100 [thread overview]
Message-ID: <87wqybhraw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20121025182332.GC5178@tarshish> (Baruch Siach's message of "Thu, 25 Oct 2012 20:23:32 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Baruch> Hi Michael,
Baruch> On Thu, Oct 25, 2012 at 07:42:26PM +0200, Michael Stieler wrote:
>> we are using buildroot for arm development. we are migrating from
>> arm926t to AM3358 and AM3359.
>>
>> i was hoping to continue to use buildroot for the processors, but i
>> cannot build the right compiler for these 2.
>>
>> in make menuconfig i choose:
>>
>> target architecture ARM (big endian)
Baruch> Why big endian? As far as I know all TI SoCs (as almost all ARM
Baruch> SoCs) are little endian.
Indeed. We already have a beaglebone (am3358) defconfig
(configs/beaglebone_defconfig).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-10-28 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:42 [Buildroot] buildroot for AM3358 AM3359 with wireless-tools shared library Michael Stieler
2012-10-25 18:18 ` Thomas Petazzoni
2012-10-25 18:23 ` Baruch Siach
2012-10-28 9:36 ` Peter Korsgaard [this message]
2012-10-30 11:35 ` Jürgen Benjamin Ronshausen
2012-10-30 22:13 ` Thomas Petazzoni
2012-10-31 11:30 ` Jürgen Benjamin Ronshausen
2012-10-31 23:06 ` Arnout Vandecappelle
2012-11-07 11:04 ` Jürgen Benjamin Ronshausen
2012-11-12 6:14 ` Arnout Vandecappelle
2012-12-28 13:21 ` 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=87wqybhraw.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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