public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC] Patch for proper Cortex-A8 cache configuration output
Date: Wed, 10 Sep 2008 16:28:07 -0700	[thread overview]
Message-ID: <20080910232807.GP21163@atomide.com> (raw)
In-Reply-To: <20080808104007.GU24923@atomide.com>

* Tony Lindgren <tony@atomide.com> [080808 03:41]:
> * Dirk Behme <dirk.behme@googlemail.com> [080807 19:38]:
> >
> > Recent ARM kernel doesn't detect and output Cortex-A8 cache  
> > configuration correctly. Result is something like this in kernel's boot 
> > messages:
> >
> > -- cut --
> > ...
> > CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
> > ...
> > CPU0: D VIPT write-through cache
> > CPU0: cache: 768 bytes, associativity 1, 8 byte lines, 64 sets
> > ...
> > -- cut --
> >
> > Catalin sent a patch for this to linux-arm-kernel list:
> >
> > http://lists.arm.linux.org.uk/lurker/message/20080704.150532.983f01ca.en.html
> >
> > Result:
> >
> > -- cut --
> > ...
> > CPU0: L1 I VIPT cache. Caches unified at level 2, coherent at level 3
> > CPU0: Level 1 cache is separate instruction and data
> > CPU0: I cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
> >       supports RA
> > CPU0: D cache: 16384 bytes, associativity 4, 64 byte lines, 64 sets,
> >       supports RA WB WT
> > CPU0: Level 2 cache is unified
> > CPU0: unified cache: 262144 bytes, associativity 8, 64 byte lines, 512  
> > sets,
> >       supports WA RA WB WT
> > ...
> > -- cut --
> >
> > Some people really like this and this patch is used in some private  
> > trees, e.g. for BeagleBoard.
> >
> > Unfortunately, RMK doesn't like the patch. He prefers to completely  
> > remove 'broken' configuration output completely.
> >
> > What's about applying this patch locally to OMAP git until upstream ARM 
> > kernel has a fix/remove solution for this?
> 
> Yeah, let's try it out next week after updating to rc2. There will be
> also move of the headers to go under plat-omap, so let's get all that
> done first.

I guess Catalin will submit his patch at some point after 2.6.28 opens.
I'll apply it l-o tree, and remove the L2 debug info we had in id.c
to clean up id.c in the future patches.

Tony

  reply	other threads:[~2008-09-10 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 16:37 [RFC] Patch for proper Cortex-A8 cache configuration output Dirk Behme
2008-08-08 10:40 ` Tony Lindgren
2008-09-10 23:28   ` Tony Lindgren [this message]
2008-09-11  8:45     ` Russell King - ARM Linux
2008-09-11 18:37       ` Tony Lindgren

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=20080910232807.GP21163@atomide.com \
    --to=tony@atomide.com \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap@vger.kernel.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