From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot and sh4
Date: Mon, 15 Nov 2010 23:26:20 +0100 [thread overview]
Message-ID: <20101115232620.201bba02@surf> (raw)
In-Reply-To: <4CE05DFF.9050906@yahoo.fr>
On Sun, 14 Nov 2010 23:09:03 +0100
trem <tremyfr@yahoo.fr> wrote:
> I've done a new version of the patch based on branch boards-cleanup
> of git://git.busybox.net/~tpetazzoni/git/buildroot
>
> This new patch could be find here :
> http://ryu.zarb.org/~trem/buildroot/0002-Add-a-qemu-device-target-sh4-r2d.patch
This patch does not follow completely the "new" way of adding board
support in Buildroot:
* The kernel configuration file should have been saved using "make
savedefconfig" in your kernel directory, so as to have a minimal
defconfig instead of this huge defconfig.
* Similarly, the Buildroot configuration file should have been saved
using "make savedefconfig" in your Buildroot directory.
With this, instead of having several tens of kilobytes of configuration
files, you'll have only a few hundred bytes of configuration.
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:[~2010-11-15 22:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 22:08 [Buildroot] buildroot and sh4 Philippe Reynes
2010-06-04 7:36 ` Thomas Petazzoni
2010-06-04 8:39 ` Pierre Ficheux
2010-06-04 9:17 ` Thomas Petazzoni
2010-06-04 10:37 ` Peter Korsgaard
2010-06-04 22:12 ` Philippe Reynes
2010-06-07 9:14 ` Phil Edworthy
2010-07-03 10:52 ` Philippe Reynes
2010-07-27 22:16 ` Philippe Reynes
2010-11-07 18:28 ` Thomas Petazzoni
2010-11-10 14:11 ` Phil Edworthy
2010-11-14 22:09 ` trem
2010-11-15 22:26 ` Thomas Petazzoni [this message]
2010-11-28 20:07 ` trem
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=20101115232620.201bba02@surf \
--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.