From: Nathan Lynch <ntl@pobox.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Roese <sr@denx.de>, linuxppc-dev@ozlabs.org, Stefan
Subject: Re: [PATCH] powerpc/4xx: Add L2 cache node to AMCC Canyonlands dts file
Date: Fri, 5 Dec 2008 15:04:48 -0600 [thread overview]
Message-ID: <20081205210448.GE6958@localdomain> (raw)
In-Reply-To: <1228475481.10722.12.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Fri, 2008-12-05 at 06:08 -0500, Josh Boyer wrote:
> > Shouldn't there also be a next-level-cache property added to the cpu
> > node that references this?
> >
> It would be nice indeed, it would allow the kernel to expose the cache
> info in sysfs
Currently the kernel only knows about the 'l2-cache' property and not
'next-level-cache'. I've got patches to fix that, will post them
soon.
prev parent reply other threads:[~2008-12-05 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 6:08 [PATCH] powerpc/4xx: Add L2 cache node to AMCC Canyonlands dts file Stefan Roese
2008-12-05 11:08 ` Josh Boyer
2008-12-05 11:11 ` Benjamin Herrenschmidt
2008-12-05 11:17 ` Stefan Roese
2008-12-05 21:04 ` Nathan Lynch [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=20081205210448.GE6958@localdomain \
--to=ntl@pobox.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@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 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).