From: Scott Wood <scottwood@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: malc <av1474@comtv.ru>,
linuxppc-dev@lists.ozlabs.org, hollis@penguinppc.org
Subject: Re: Probing for native availability of isel from userspace
Date: Mon, 24 Sep 2012 19:40:46 -0500 [thread overview]
Message-ID: <1348533646.25867.33@snotra> (raw)
In-Reply-To: <1348533123.1132.102.camel@pasglop> (from benh@kernel.crashing.org on Mon Sep 24 19:32:03 2012)
On 09/24/2012 07:32:03 PM, Benjamin Herrenschmidt wrote:
> On Mon, 2012-09-24 at 18:55 -0500, Scott Wood wrote:
> > The ISA says that isel is "Category: Phased-In (sV2.06)" -- are =20
> there
> > any 2.06 chips that don't have it?
>=20
> I believe "malc" is interested in knowing about pre-2.06 chips that =20
> have
> it.
You said to key off of 2.06 plus a PVR whitelist for pre-2.06 chips =20
that have it. Wouldn't you also need a PVR blacklist for 2.06 chips =20
that don't have it (unless there are no such things)? Or if one is =20
only interested in pre-2.06 chips, why check for 2.06 at all?
-Scott=
next prev parent reply other threads:[~2012-09-25 0:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 20:05 Probing for native availability of isel from userspace malc
2012-09-22 7:26 ` Segher Boessenkool
2012-09-22 10:12 ` malc
2012-09-22 10:21 ` Gabriel Paubert
2012-09-22 15:37 ` malc
2012-09-22 16:13 ` David Gibson
2012-09-22 19:08 ` Segher Boessenkool
2012-09-22 19:55 ` Benjamin Herrenschmidt
2012-09-22 20:17 ` malc
2012-09-23 1:46 ` Segher Boessenkool
2012-09-24 7:55 ` Gabriel Paubert
2012-09-24 7:58 ` Benjamin Herrenschmidt
2012-09-24 8:06 ` Gabriel Paubert
2012-09-24 9:41 ` Benjamin Herrenschmidt
2012-09-25 13:17 ` Segher Boessenkool
2012-09-25 20:59 ` Benjamin Herrenschmidt
2012-09-26 0:17 ` Kumar Gala
2012-09-24 23:55 ` Scott Wood
2012-09-25 0:32 ` Benjamin Herrenschmidt
2012-09-25 0:40 ` Scott Wood [this message]
2012-09-25 0:47 ` malc
2012-09-25 0:50 ` Scott Wood
2012-09-25 13:31 ` Segher Boessenkool
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=1348533646.25867.33@snotra \
--to=scottwood@freescale.com \
--cc=av1474@comtv.ru \
--cc=benh@kernel.crashing.org \
--cc=hollis@penguinppc.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.