From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: Cortex-m3 Kernel Port.
Date: Mon, 25 Jan 2010 11:41:59 +0000 [thread overview]
Message-ID: <1264419719.6275.15.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20100125112057.GA3536@shareable.org>
On Mon, 2010-01-25 at 11:20 +0000, Jamie Lokier wrote:
> Catalin Marinas wrote:
> > On Mon, 2010-01-25 at 06:15 +0000, Sasa Sasa wrote:
> > > What is the status of the cortex-m3 kernel port ? Is it merged to
> > > mailine ?
> >
> > No and I wasn't planning to unless there are more people using it to be
> > worth the maintenance effort (the Cortex-M3 platforms I've seen have too
> > little RAM to be able to run Linux).
>
> How much do they have? People are running uClinux in 8-16MB; it's
> tight squeeze but sometimes worth it. If it has an MMU it would need
> a bit less memory.
Cortex-M3 doesn't have an MMU. I managed to run it in 2MB but not many
commands were successful. I think from 4MB onwards it should be
acceptable.
--
Catalin
prev parent reply other threads:[~2010-01-25 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 6:15 Cortex-m3 Kernel Port Sasa Sasa
2010-01-25 11:06 ` Catalin Marinas
2010-01-25 11:20 ` Jamie Lokier
2010-01-25 11:41 ` Catalin Marinas [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=1264419719.6275.15.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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