From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM946, u-boot and linux
Date: Tue, 27 Jul 2004 18:36:24 -0700 [thread overview]
Message-ID: <c3d0340b040727183672fbbf40@mail.gmail.com> (raw)
In-Reply-To: <20040727220032.B4494C109F@atlas.denx.de>
Dear Wolfgang,
On Wed, 28 Jul 2004 00:00:27 +0200, Wolfgang Denk <wd@denx.de> wrote:
> > 1. uclinux or linux?
>
> Let's rephrase it: the only chance you have on a MMU-less system is
> by using uCLinux. For standard Linux a working MMU is mandatory.
>
> Note that it seens that uCLinux has already been ported to the
> ARM946.
Thanks. Now I know what I need to focus.
> > 2. Boot loader?
> > with MMU, such as 926. Or more general question: does u-boot support
> > processors without MMU? From my ppc experience I know MMU is enabled
> > on u-boot.
>
> And you are wrong: U-Boot does NOT use the MMU on PPC. [At least not
> on all processors, and if then not for virtual memory but just to
> play dirt^H^H^H^Hclever tricks with the data cache.]
Oh. I see. Enabling MMU on PPC is just some dirt & clever tricks with
the data cache. I saw the code to enable MMU in start.S. Hmmm...maybe
a bit detail is more helpful to understand why MMU is enabled. Maybe I
need to go back to the processor's user guide.
> > Does ELDK support ARM946? ELDK supports arm920. ELDK can be used for
> > arm946 if its core is compatible with arm920's. If ELDK doesn't
>
> You can use the cross toolchain, but the ative target tools will of
> course not run as they require a standard Linux kernel, not uCLinux.
?? What target tools are you talking about? I thought the target tools
refer to cross compiler, debugger, etc..
Best regards,
-Shawn.
next prev parent reply other threads:[~2004-07-28 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 18:03 [U-Boot-Users] ARM946, u-boot and linux Shawn Jin
2004-07-27 22:00 ` Wolfgang Denk
2004-07-28 1:36 ` Shawn Jin [this message]
2004-07-28 8:53 ` Wolfgang Denk
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=c3d0340b040727183672fbbf40@mail.gmail.com \
--to=shawnxjin@gmail.com \
--cc=u-boot@lists.denx.de \
/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