linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: benh@kernel.crashing.org
Cc: John Bonesio <john.bonesio@xilinx.com>, Linuxppc-dev@ozlabs.org
Subject: Re: ppc440 caches - change proposal [RFC]
Date: Tue, 8 Apr 2008 17:15:44 -0600	[thread overview]
Message-ID: <fa686aa40804081615n284aa750n12ceb0bf1d1bcce1@mail.gmail.com> (raw)
In-Reply-To: <1207695415.14711.11.camel@pasglop>

On Tue, Apr 8, 2008 at 4:56 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
>
>  On Tue, 2008-04-08 at 15:53 -0700, John Bonesio wrote:
>  > I was thinking it might be good to have the kernel initialize these
>  > cache control registers in it's own start up code. Or perhaps this
>  > could be done in the kernel's simple bootloader. We could probably put
>  > this change in a Xilinx specific startup file, but this change doesn't
>  > seem specific to Xilinx FPGA boards.
>
>  The kernel's wrapper would be a good place to put that I suspect. That's
>  the kind of thing that should be provided as a "library" function to be
>  optionally called by platform code. Either in the wrapper or the main
>  kernel platform code.

Code is already queued up for 2.6.26 to do exactly this on ppc405
virtex platforms.  We can do the same thing for 440.  Look at
virtex405-head.S in the following patch:

http://patchwork.ozlabs.org/linuxppc/patch?person=486&id=17410

Cheers,
g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-04-08 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 22:53 ppc440 caches - change proposal [RFC] John Bonesio
2008-04-08 22:56 ` Benjamin Herrenschmidt
2008-04-08 23:15   ` Grant Likely [this message]
2008-04-09  0:47     ` Josh Boyer
2008-04-09 18:00     ` John Bonesio
2008-04-09 19:50       ` Grant Likely
2008-04-10 18:03         ` Josh Boyer

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=fa686aa40804081615n284aa750n12ceb0bf1d1bcce1@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=benh@kernel.crashing.org \
    --cc=john.bonesio@xilinx.com \
    /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).