From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] XBurst CPU by Ingenic
Date: Tue, 03 Feb 2009 09:55:18 +0100 [thread overview]
Message-ID: <87hc3bgart.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <84687A6B-E461-4916-A313-3E441B940217@laptouchinc.com> (Daniel Jabbour's message of "Mon\, 2 Feb 2009 15\:31\:03 -0500")
>>>>> "Daniel" == Daniel Jabbour <daniel@laptouchinc.com> writes:
Daniel> Hi,
Daniel> Has anyone used buildroot with the XBurst CPU by Ingenic? It's a MIPS
Daniel> 32 compatible CPU which Ingenic has released a toolkit for on their
Daniel> site (http://www.ingenic.cn/eng/productServ/kfyd/Linux/
Daniel> pfCustomPage.aspx). It seems pretty straight forward, but I'm
Daniel> wondering if I need to use their toolchain or if I can simply use
Daniel> buildroot and select MIPS as the architecture.
Daniel> My question is basically: Would you recommend using the Ingenic
Daniel> toolchain or simply a generic MIPS-32 one?
No idea, but the simplest approach would probably to just do a quick
BR compilation with the generic mips32 compiler and check that it all
works.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-02-03 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 20:31 [Buildroot] XBurst CPU by Ingenic Daniel Jabbour
2009-02-03 8:55 ` Peter Korsgaard [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=87hc3bgart.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