From: Keith Adams <kma@cs.brown.edu>
To: linux-mm@kvack.org
Subject: Re: Linux Without MMU
Date: Mon, 6 Dec 1999 10:56:40 -0500 [thread overview]
Message-ID: <19991206105640.B11531@cs.brown.edu> (raw)
In-Reply-To: <199912061545.HAA27422@ns1.filetron.com>; from AndreaE on Mon, Dec 06, 1999 at 07:45:56AM -0800
On Mon, Dec 06, 1999 at 07:45:56AM -0800, AndreaE wrote:
> AndreaE <AndreaE@linuxstart.com> wrote:
> Hi ,
> ..i'm working on Linux Kernel porting on HardWare Without MMU. This is not impossible ( uCLinux Es. ), but i'm bored to read thousend &
> thousend of code without a Guide Line. My target is port a full playable linux apps on ARM7TDMI ( very low cost & hi performance CPU but without mmu ). I'm using a uCSimm like example. I've difficulties to understand the new gadget from kernel 2.0.38 (uses by uCSim & Co. ) and kernel 2.2.12 with ARM support.
>
> Is There anyone that have some experience with this problem or have some tips to tell me ???
I'm not sure what you mean by "uCSimm-like example," or "new gadget,"
but I did a port to the i960 that was very similar to your port. You
have the added advantage of there already being an ARM port of the
standard kernel, so there will be less architecture manual spelunking
for you to do.
I'm afraid there isn't very much useful documentation about the design
of the (uC)linux kernel; I had to figure it out the hard way. If you'd
like a book to introduce you to the kernel, the most helpful one I
found was the O'Reilly book _Writing Linux Device Drivers_. Steer clear
of the _Linux Kernel Internals_ book; it is, if I recall correctly,
misleading in important respects.
> Is There anyone interesting to help me to do it ??
If you've got hardware to donate, I might be able to help.
Keith
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-12-06 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 15:45 AndreaE
1999-12-06 15:56 ` Keith Adams [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=19991206105640.B11531@cs.brown.edu \
--to=kma@cs.brown.edu \
--cc=linux-mm@kvack.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