From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Best way of building for unknown architecture
Date: Fri, 17 Aug 2012 19:43:10 +0200 [thread overview]
Message-ID: <20120817194310.25198340@skate> (raw)
In-Reply-To: <760828.46392.bm@smtp116.mail.ukl.yahoo.com>
Le Fri, 17 Aug 2012 18:39:55 +0100,
Kevin Chadwick <ma1l1ists@yahoo.co.uk> a ?crit :
> Openembedded, T2 and NuttX seem to support arm7-m (cortex-m3)
> but I like buildroot. Is the best way of building to use Little
> endian generic and the GCC compiler or is it fairly easy to add
> a new architecture variant that I could possibly send a diff
> for later.
Adding a new target architecture variant just requires a few lines of
code in target/Config.in.arch. If you give some hints, I'm pretty sure
someone will be kind enough to help you making the necessary changes.
> Similarly is it easier to use the kernel patch config and kernel
> config options or is it fairly easy to add a Target
> architecture.
In 'make menuconfig', Kernel submenu, there is an option to point to
kernel patches needed for your platform.
Best regards,
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-17 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 17:39 [Buildroot] Best way of building for unknown architecture Kevin Chadwick
2012-08-17 17:43 ` Thomas Petazzoni [this message]
2012-08-20 16:27 ` Kevin Chadwick
2012-08-21 7:35 ` Thomas Petazzoni
2012-08-24 15:58 ` Kevin Chadwick
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=20120817194310.25198340@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.