From: Ben Kloosterman <bklooste@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to create a non mmu toolchain
Date: Wed, 5 May 2010 15:10:07 +0800 [thread overview]
Message-ID: <03ec01caec22$0049a4f0$00dceed0$@com> (raw)
In-Reply-To: <876332df2k.fsf@macbook.be.48ers.dk>
Thx for your reply .
So which chain supports Nommu ?
Br no mmu support
Crosstool no mmu support.
Ct-ng no mmu
Uclinux support but requires a no mmu tool chain.
Building a toolchain by hand.
The reason why we dont want to use an mmu is complex , there is a thread on
it in ucLinux but basically building a type safe , memory safe micro kernel
OS since we run a single address space with compiler based checks an MMU
just becomes an overhead. Rather than the green field code we have been
working on for 2 years we can start with uClinux which will help things
along .
Regards,
Ben
>-----Original Message-----
>From: Peter Korsgaard [mailto:jacmet at gmail.com] On Behalf Of Peter
>Korsgaard
>Sent: Wednesday, May 05, 2010 2:43 PM
>To: bklooste at gmail.com
>Cc: buildroot at busybox.net
>Subject: Re: How to create a non mmu toolchain
>
>>>>>> "Ben" == Ben Kloosterman <bklooste@gmail.com> writes:
>
> Ben> How to create an i386/686 or x86-64 No mmu ( eg ARCH-USE-MMU =
>false)
> Ben> toolchain ?
>
>Sorry, we don't have any non-mmu support. Why would you not want to use
>the MMU on the i386/x86-64?
>
>--
>Bye, Peter Korsgaard
prev parent reply other threads:[~2010-05-05 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 21:11 [Buildroot] [git commit master] mplayer: disable parallel builds (make -jX) Peter Korsgaard
2010-05-04 22:39 ` [Buildroot] How to create a non mmu toolchain Ben Kloosterman
2010-05-05 6:42 ` Peter Korsgaard
2010-05-05 7:10 ` Ben Kloosterman [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='03ec01caec22$0049a4f0$00dceed0$@com' \
--to=bklooste@gmail.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