linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "John Bonesio" <john.bonesio@xilinx.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: ppc440 caches - change proposal [RFC]
Date: Wed, 9 Apr 2008 13:50:43 -0600	[thread overview]
Message-ID: <fa686aa40804091250u1f532cddj9e3897969a98349c@mail.gmail.com> (raw)
In-Reply-To: <20080409180042.511531370055@mail134-sin.bigfish.com>

On Wed, Apr 9, 2008 at 12:00 PM, John Bonesio <john.bonesio@xilinx.com> wrote:
> Hi Grant,
>
>  I have a question about your patch. It appears as if the cache setup code is
> in a file that would be used only on Xilinx FPGA devices.

That is correct.

>
>  I understand that many people are using a bootloader that already sets up the
> cache for the kernel, but I'm wondering if Xilinx boards are really a special
> case, or if there may be other non-Xilinx related systems that would also not
> be using a bootloader.

I think there are very few cases of platforms not using some form of firmware.

>
>  I also understand the desire to avoid code that does the same work more than
> once, but I wonder if in this case, it's creating too strong a dependence on
> the specific behavior of a certain bootloader.
>  I also wonder if arch/powerpc is being made more complex by trying to split
>  out this code change into a Xilinx specific area, when the change could just
> be rolled into head_40x.S and we could do away with virtex405-head.S.

In general, I think that the wrapper does not want to touch the cache
settings.  In the common case where firmware exists and sets up the
cache then to turn off the cache again would throw away what firmware
already had in cache and slow down the boot.

That being said, I'm not the bootwrapper expert.  If other think that
it belongs in head_40x.S then I have no objections.

Josh, any thoughts?

Cheers,
g.


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

  reply	other threads:[~2008-04-09 19:50 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
2008-04-09  0:47     ` Josh Boyer
2008-04-09 18:00     ` John Bonesio
2008-04-09 19:50       ` Grant Likely [this message]
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=fa686aa40804091250u1f532cddj9e3897969a98349c@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Linuxppc-dev@ozlabs.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).