All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram
Date: Tue, 21 May 2013 22:07:20 +0200	[thread overview]
Message-ID: <201305212207.20234.marex@denx.de> (raw)
In-Reply-To: <1369165375.12900.44.camel@host5.omatika.ru>

Dear Sergey Yanovich,

> Dear Marek Vasut,
> 
> On Tue, 2013-05-21 at 21:24 +0200, Marek Vasut wrote:
> > I'd love to have a uniform way to do this cache thing, really ...
> 
> Requoting the spec 'The PXA27x processor cache configuration is
> identical to that of the PXA255 processor'. It looks safe to configure
> all PXA2XX chipsets this way.
> 
> Maybe I am missing something, but SPL is no exception in this case.

The OneNAND has 1kbyte limit on code it will directly address when booting from 
it, you can't even make generate the MMU table there.

> > Not really, enabling dcache altogether and marking DRAM region as cached
> > would be much better.
> > 
> > > Repeating my hedge, I don't see the full picture,
> > > yet. It may well be impossible (if U-Boot needs more than 32 kB of
> > > stack)
> > 
> > No way.
> > 
> > > or not worth the effort (if the gain is too small).
> > 
> > The larger gain would be from fixing the U-Boot drivers for PXA to work
> > well with DCache ;-) Then the speedup would really be plenty
> > significant, this can be well confirmed on many other ARM chips.
> 
> I have plans to dig deeper into this after I complete the current
> project. Faster boot is always a good thing. Thanks for explaining in
> details.

Sure, yet I think I just piled work onto you ;-)

Best regards,
Marek Vasut

  reply	other threads:[~2013-05-21 20:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 22:06 [U-Boot] [PATCH] arm: pxa: PXA270 D-Cache as ram Sergey Yanovich
2013-05-21 10:39 ` Marek Vasut
2013-05-21 10:42   ` Sergey Yanovich
2013-05-21 10:54     ` Marek Vasut
2013-05-21 11:23       ` Sergey Yanovich
2013-05-21 11:38         ` Marek Vasut
2013-05-21 11:56           ` Sergey Yanovich
2013-05-21 15:00             ` Marek Vasut
2013-05-21 16:31               ` Sergey Yanovich
2013-05-21 19:02                 ` Marek Vasut
2013-05-21 19:18                   ` Sergey Yanovich
2013-05-21 19:24                     ` Marek Vasut
2013-05-21 19:42                       ` Sergey Yanovich
2013-05-21 20:07                         ` Marek Vasut [this message]
2013-05-21 20:24                           ` Sergey Yanovich
2013-05-21 21:38                             ` Marek Vasut
2013-05-22 13:02                               ` Sergey Yanovich
2013-05-22 13:04                                 ` Marek Vasut
2013-05-22 13:21                                   ` Sergey Yanovich
2013-05-22 13:54                                     ` Marek Vasut
2013-05-23 17:43                               ` Mike Dunn

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=201305212207.20234.marex@denx.de \
    --to=marex@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.