From: Dan Malek <dan@netx4.com>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: linuxppc-embedded@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC Cache Flush and Invalidate Routines
Date: Wed, 08 Dec 1999 18:46:16 -0500 [thread overview]
Message-ID: <384EEDC8.EDDABF3A@netx4.com> (raw)
In-Reply-To: Pine.SGI.4.10.9912081721580.155726-100000@brule.borg.umn.edu
Grant Erickson wrote:
> I'd like to have a kernel that will boot on any 4xx-based board (maybe or
> maybe not realistic), so because the 403 uses 16 byte lines and the 405
> uses 32 byte lines, I need a dynamic solution such as the one Gary
> suggested.
So, let's just make them kernel variables and load them. What's
a few extra cycles here and there :-). You just end up moving
the #defines to one of the kernel setup files......
Another alternative that requires some investigation would be
using the 16 byte line size on the 405. My concern is there may
be alignment restrictions, but if it works all it costs you is
an extra (and ignored) cache instruction. If this would work
on all processors (and my puke green book indicates it should),
it would be a nice modification to the C library. Those big-assed
processors won't care if they execute a few more instructions, and
the little kids will work with caches enabled.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-08 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 22:45 PPC Cache Flush and Invalidate Routines Grant Erickson
1999-12-08 23:02 ` Gary Thomas
1999-12-08 23:58 ` Daniel L. Taylor
1999-12-09 0:12 ` Dan Malek
1999-12-08 23:25 ` Grant Erickson
1999-12-08 23:46 ` Dan Malek [this message]
1999-12-12 19:56 ` Noah Misch
1999-12-13 19:51 ` Dan Malek
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=384EEDC8.EDDABF3A@netx4.com \
--to=dan@netx4.com \
--cc=grant@lcse.umn.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@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).