linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jim Terman <terman@ddi.com>
To: Kumar Gala <kumar@chaos.ph.utexas.edu>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: question about altivec registers
Date: Tue, 26 Oct 1999 14:52:55 -0700 (PDT)	[thread overview]
Message-ID: <199910262152.OAA02956@sade.ddi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9910252336320.2381-100000@chaos.ph.utexas.edu>


Will the linuxppc kernal as it is right now save the AltiVec registers
if we enable the MSR VEC bit.  I've been trying to follow the other messages
on this subject, but I'm not clear.

Kumar Gala writes:
> 
> The linux kernel as is will not effect the AltiVec registers in any way.
> However, there is a minor change to the kernel that will be required.  You
> will need to enable the MSR VEC bit (bit 6 in the MSR) to tell the
> processor that the AltiVec Unit is available (this is similar to the MSR
> FP bit).  If the bit is not set the processor will generate an AltIVec
> Unavailable exception which will be trapped (incorrectly) as an unknown
> 0xf00 exception
> 
> the 0xf00 exception is for the performance monitors
> and 0xf20 in the AltiVec unavailable exception.
> 
> All if these details are documented in the AltiVec Programming Environ
> Manual (available from the Motorola Website).  
> 
> If you need any help getting a simple kernel up and running for running
> single altiVec enabled processes let me know.
> 
> - kumar gala
> 
> 
> ignorance is bliss.
> 
> 
> 
-- 
______________________________________________________________________________
Jim Terman       |   323 Vintage Park Dr.   |   Voice: (650) 356-5446
terman@ddi.com   |   Foster City, CA        |   Fax:   (650) 356-5490
Diab-SDS, Inc.   |   94404                  |   web site - http://www.ddi.com

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

  reply	other threads:[~1999-10-26 21:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-25 20:51 question about altivec registers Jim Terman
1999-10-25 22:27 ` Claude Robitaille
1999-10-25 22:31   ` Jim Terman
1999-10-25 22:44     ` erik cameron
1999-10-25 23:28     ` Claude Robitaille
     [not found]     ` <Pine.LNX.4.10.9910251916060.5902-100000@modemcable220.93-200-24.mtl.mc.vi deotron.net>
1999-10-25 23:53       ` Rob Barris
1999-10-26 18:22         ` Geert Uytterhoeven
1999-10-26 22:13           ` Rob Barris
1999-10-26 22:38           ` Tom Vier
1999-10-26 22:03         ` Tom Vier
1999-10-26  4:42 ` Kumar Gala
1999-10-26 21:52   ` Jim Terman [this message]
1999-10-26 22:43     ` Kumar Gala
1999-10-27  8:58       ` Adrian Cox
1999-10-27 13:21         ` Gabriel Paubert
1999-10-27 16:05           ` Geert Uytterhoeven
1999-10-27 18:23           ` Kumar Gala
1999-10-27 22:39           ` Tony Mantler
1999-10-28 11:01             ` Gabriel Paubert
1999-10-28 21:20               ` Tony Mantler
1999-10-29 11:58                 ` Benjamin Herrenschmidt
1999-10-29 12:49                 ` Gabriel Paubert
1999-10-30  4:14                   ` Tony Mantler

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=199910262152.OAA02956@sade.ddi.com \
    --to=terman@ddi.com \
    --cc=kumar@chaos.ph.utexas.edu \
    --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).