From: "Hyok S. Choi" <hyok.choi@samsung.com>
To: uClinux development list <uclinux-dev@uclinux.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org
Cc: CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
rmk@arm.linux.org.uk
Subject: [PATCH] the MPU/noMMU support for ARM Linux 2.6.11.6 (-hsc0)
Date: Fri, 01 Apr 2005 15:15:49 +0900 [thread overview]
Message-ID: <0IE900JYS84MQI@mmp1.samsung.com> (raw)
In-Reply-To:
Greetings,
I'm glad to announce the MPU and noMMU support patch for ARM against
2.6.11.6 at:
http://opensrc.sec.samsung.com/download/linux-2.6.11.6-hsc0.patch.gz
Actually the patch was "armnommu" architecture patch by 2.6.9, but it is
just merged into "arm" architecture, and provides selection option, "MMU"
for linux and "MPU", "NONE" for uclinux. It means that you can choose "MMU"
or even "NONE" for your MMU based arm platform with a few modification (i.e.
virtual addr --> physical addr), if you want to use "singular address space"
which is proven to have performance improvement. (I'd like to provide some
benchmark result on same h/w platform for both cases.)
some addtional MPU support API is pending to support new features like
memory protection for uclinux, but I need more suggestions on that.
You can reach the project at : http://opensrc.sec.samsung.com/
currently officially supported platforms are : s3c24a0, s5c7375, atmel,
espd_s3c510b, P2001, s3c3410, s3cb0x.
Best Regards,
Hyok
---
CHOI, HYOK-SUNG
Engineer (Kernel/System Architecture)
Digital Media R&D Center, Samsung Electronics Co.,Ltd.
tel: +82-31-200-8594 fax: +82-31-200-3427
e-mail: hyok.choi@samsung.com
[Linux 2.6 ARM MPU/noMMU Kernel Maintainer] http://opensrc.sec.samsung.com/
reply other threads:[~2005-04-01 6:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0IE900JYS84MQI@mmp1.samsung.com \
--to=hyok.choi@samsung.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=uclinux-dev@uclinux.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
all inboxes | Powered by JetHome®