From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Development around Coldfire
Date: Tue, 10 Apr 2012 18:10:44 +0200 [thread overview]
Message-ID: <cover.1334074065.git.thomas.petazzoni@free-electrons.com> (raw)
Hello,
The work enclosed in the patches is not fully-working yet, but I
wanted to share it so that others can help, and to avoid others in
trying to do the same thing.
Basically, the goal of this patch set is to add a defconfig for the
MCF5208 Coldfire platform emulated by Qemu, which is a non-MMU
platform.
The proposed defconfig generates a system where the kernel boots, but
panics when the first userspace program exits (the kernel complains
that someone tried to kill init).
I think patches 1 to 4 could be merged now, while the 5th patch
(adding the defconfig) needs more work to fix this problem before
being submitted. The other annoying part is that a patch for Qemu is
also needed (it is part of this 5th patch).
Note that I have also done a similar work on the AT91 ARM noMMU
platform emulated by SkyEye. I hope to send the patches soon.
Thomas
The following changes since commit 8876b6751e0bc19a3754290061808f0f8420708e:
Fix makedevs to allow longer path names (2012-04-08 19:46:52 +0200)
are available in the git repository at:
git://git.free-electrons.com/users/thomas-petazzoni/buildroot.git for-2012.05/coldfire
Thomas Petazzoni (5):
arch: re-enable m68k and add a few architecture variants
toolchain: add Coldfire external toolchain from Sourcery CodeBench
toolchain: add m68k to the list of arch that can work without MMU
busybox: enable useful hush suboptions
board: add support for Coldfire MCF5208EVB board emulated by Qemu
.../qemu/m68k-mcf5208evb/linux-3.3-sw-ustack.patch | 25 +++++++
board/qemu/m68k-mcf5208evb/linux-3.3.config | 71 ++++++++++++++++++++
.../qemu-mcfint-masking-support.patch | 42 ++++++++++++
board/qemu/m68k-mcf5208evb/readme.txt | 14 ++++
configs/qemu_m68k_mcf5208_evb_defconfig | 14 ++++
package/busybox/busybox.mk | 5 ++
target/Config.in.arch | 41 +++++++++++-
toolchain/toolchain-common.in | 2 +-
toolchain/toolchain-external/Config.in | 41 +++++++++++
toolchain/toolchain-external/ext-tool.mk | 3 +
10 files changed, 256 insertions(+), 2 deletions(-)
create mode 100644 board/qemu/m68k-mcf5208evb/linux-3.3-sw-ustack.patch
create mode 100644 board/qemu/m68k-mcf5208evb/linux-3.3.config
create mode 100644 board/qemu/m68k-mcf5208evb/qemu-mcfint-masking-support.patch
create mode 100644 board/qemu/m68k-mcf5208evb/readme.txt
create mode 100644 configs/qemu_m68k_mcf5208_evb_defconfig
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2012-04-10 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 16:10 Thomas Petazzoni [this message]
2012-04-10 16:10 ` [Buildroot] [PATCH 1/5] arch: re-enable m68k and add a few architecture variants Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 2/5] toolchain: add Coldfire external toolchain from Sourcery CodeBench Thomas Petazzoni
2012-04-17 22:54 ` Arnout Vandecappelle
2012-04-18 8:25 ` Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 3/5] toolchain: add m68k to the list of arch that can work without MMU Thomas Petazzoni
2012-04-10 17:28 ` Gustavo Zacarias
2012-04-10 16:10 ` [Buildroot] [PATCH 4/5] busybox: enable useful hush suboptions Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 5/5] board: add support for Coldfire MCF5208EVB board emulated by Qemu 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=cover.1334074065.git.thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox