From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Dirk Behme <dirk.behme@googlemail.com>, linux-omap@vger.kernel.org
Subject: Re: [RFC] Patch for proper Cortex-A8 cache configuration output
Date: Thu, 11 Sep 2008 11:37:29 -0700 [thread overview]
Message-ID: <20080911183728.GM21163@atomide.com> (raw)
In-Reply-To: <20080911084543.GB26078@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [080911 01:46]:
> On Wed, Sep 10, 2008 at 04:28:07PM -0700, Tony Lindgren wrote:
> > 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.
>
> As I've said on the main ARM lists where I've given reasons, I'm against
> extending this stuff, and it is my intention to remove it completely.
> It was only added because it was relatively simple and easy to print the
> information.
>
> However, with ARMs attitude of breaking configuration register formats
> willy nilly, it's just not worth having the additional complexity to
> try to work out which format we have, and decode that format.
>
> For all we know, come the next ARM architecture revision, these registers
> will have completely changed their format again. So much for providing
> software with an easy way to determine the parameters of the core.
>
> It's just not worth the complexity and effort to try and decode this
> information for no other purpose than a few printk's.
Hmm, people need to see what's enabled though.
For later ARMs, would it make sense to have some arm_l2_init() function
that would get called from mach specific init to set the timings and enable
L2? That function could then dump the cache configuration too.
Tony
prev parent reply other threads:[~2008-09-11 18:37 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
2008-09-11 8:45 ` Russell King - ARM Linux
2008-09-11 18:37 ` Tony Lindgren [this message]
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=20080911183728.GM21163@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@googlemail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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