From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Abraham vd Merwe <abraham@2d3d.co.za>
Cc: Linux on PowerPC Developers Mail List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: looking for documentation on porting Linux to PowerPC platforms
Date: 05 Dec 2002 10:33:18 +0100 [thread overview]
Message-ID: <1039080798.651.54.camel@zion> (raw)
In-Reply-To: <20021205105400.B3899@crystal.2d3d.co.za>
> What about caches? Do you care whether caching is enabled or not?
Not really. We do enable L1 on "common" desktop CPUs, and machine
specific code may do more with L2 or L3 if any. It's up to you to
either setup additional caches prior to entering the kernel, or from
your machine init code.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-12-05 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:38 looking for documentation on porting Linux to PowerPC platforms Abraham vd Merwe
[not found] ` <20021204192129.GA8996@mail.cryptoapps.com>
2002-12-05 8:48 ` Abraham vd Merwe
2002-12-05 18:35 ` Chris Zimman
[not found] ` <1039025018.651.43.camel@zion>
2002-12-05 8:54 ` Abraham vd Merwe
2002-12-05 9:33 ` Benjamin Herrenschmidt [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=1039080798.651.54.camel@zion \
--to=benh@kernel.crashing.org \
--cc=abraham@2d3d.co.za \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).