From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Nuss <nmx@fromtheshadows.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Using PVR value after boot?
Date: Sat, 10 Nov 2007 08:07:24 +1100 [thread overview]
Message-ID: <1194642444.21340.16.camel@pasglop> (raw)
In-Reply-To: <a340dd0e0711091239mdf1b772l1d5a8208f7def4f5@mail.gmail.com>
On Fri, 2007-11-09 at 15:39 -0500, Mike Nuss wrote:
> I'm writing a module for the Security/KASUMI function on the
> PPC440EPx-S and PPC440GRx-S. This relies on checking the PVR value at
> runtime, which is done early on in the boot process. What would be
> the correct way to check which CPU is present during module
> initialization?
Checking the PVR can be done at any time, though a better option would
be to put something in device-tree of course :-)
Ben.
next prev parent reply other threads:[~2007-11-09 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 20:39 Using PVR value after boot? Mike Nuss
2007-11-09 21:07 ` Benjamin Herrenschmidt [this message]
2007-11-09 21:13 ` 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=1194642444.21340.16.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nmx@fromtheshadows.net \
/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).