linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benjamin.herrenschmidt@wanadoo.fr>
To: <linuxppc-commit@fsmlabs.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PVR hell
Date: Tue, 27 Mar 2001 15:25:05 +0200	[thread overview]
Message-ID: <20010327132505.23073@mailhost.mipsys.com> (raw)
In-Reply-To: <20010327132106.15522@mailhost.mipsys.com>


>
>I'd like to get this all cleaned up. The best way to acheive that is I
>beleive a bit similar to what Apple does in Darwin: a table with mask/
>value pairs used to "match' the PVR. The table will then give you the CPU
>name, eventually a pointer to some early init code, etc... and a bitmask
>of CPU "features". This bitmask can then be used for things like "has
>L2CR", "has Altivec", "has L3", "has reliable TAU", etc...

Obviously, my intend is to have the table lookup done only once during
kernel boot (head.S), and all further code relying on the table index & CPU
features bit mask retreived at this point to display CPU name, get specific
CPU features, call CPU init code (for cache init, etc...).

I'm pretty sure some bits of head.S would benefit from it too ;)

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-03-27 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 13:21 PVR hell Benjamin Herrenschmidt
2001-03-27 13:25 ` Benjamin Herrenschmidt [this message]
2001-03-27 15:36 ` Gabriel Paubert
2001-03-27 19:51   ` Dan Malek
2001-03-27 22:51     ` Benjamin Herrenschmidt
2001-03-28  5:43       ` Dan Malek
2001-03-28 11:46         ` Benjamin Herrenschmidt

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=20010327132505.23073@mailhost.mipsys.com \
    --to=benjamin.herrenschmidt@wanadoo.fr \
    --cc=linuxppc-commit@fsmlabs.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).