linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Marmier <daniel.marmier@lightning.ch>
To: Dan Malek <dan@netx4.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Altivec on 2.4.xx?
Date: Fri, 28 Jul 2000 18:57:30 +0200	[thread overview]
Message-ID: <3981BB7A.23043170@lightning.ch> (raw)
In-Reply-To: 39819D52.DAC049B4@embeddededge.com


Dan Malek wrote:
> This is a PowerPC architecture definition. It isn't unique to the MPC8xx,
> as I am obviously using a 7400 with Altivec here.

The exception I was talking about is _implementation specific_, which makes
it MPC8xx unique. I do not use Altivec, but I am afraid there could be
problems even without it. I could not find out whether the Data TLB Miss
exception sets the DSISR, but DataStoreTLBMiss can branch to DataAccess,
wich passes the DSISR to do_page_fault. Phew, hope I was clearer :-)
Anyway, I will look at this exception with care before telling more.

> Having the common page fault handler is a good thing, we just have
> to make sure we extract the information properly from the appropriate
> register.

Of course it is a good thing. I was just suggesting a way of retrieving
this information properly from do_page_fault.

> I thought there was more (than none :-) development happening with
> Altivec on PowerPC Linux.  Maybe tiny test applications will work,
> but my MPEG-2 decoder won't.

Sorry, only 8xx here :-(


				Daniel Marmier

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

      reply	other threads:[~2000-07-28 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-28  1:15 Altivec on 2.4.xx? Dan Malek
2000-07-28  7:24 ` Daniel Marmier
2000-07-28 14:48   ` Dan Malek
2000-07-28 16:57     ` Daniel Marmier [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=3981BB7A.23043170@lightning.ch \
    --to=daniel.marmier@lightning.ch \
    --cc=dan@netx4.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).