From: "Jeffrey W. Baker" <jwbaker@acm.org>
To: Paul Mackerras <paulus@samba.org>
Cc: <mlan@cpu.lu>, <linuxppc-dev@lists.linuxppc.org>,
<debian-powerpc@lists.debian.org>
Subject: Re: Call for help: altivec-enabled vlc
Date: Tue, 28 Aug 2001 07:19:43 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0108280718010.217-100000@desktop> (raw)
In-Reply-To: <15243.36729.335303.936811@cargo.ozlabs.ibm.com>
On Tue, 28 Aug 2001, Paul Mackerras wrote:
> Michel Lanners writes:
>
> > However, there's something wrong with the IDCT code; the output is
> > essentially garbage. Makes for some interesting visual effects, but
> > that's about it....
>
> Here is my altivec-enabled IDCT, in assembler. It does everything
> internally in floating point so there is no need for scaling. It
> exports two procedures:
>
> void idct_block_copy_altivec(int16_t *dct_block, uint8_t *dest, int stride);
> void idct_block_add_altivec(int16_t *dct_block, uint8_t *dest, int stride);
>
> stride is the offset between successive rows of dest. It does an IDCT
> of the 8x8 block of 16-bit integers at *dct_block, and either puts the
> result in an 8x8 block at *dest or adds it to the block at *dest.
> dct_block has to be 16-byte aligned. And no, it hasn't been
> _deliberately_ obfuscated. :)
>
> I use this in mpeg2dec (actually a hacked version that I use to play
> videos off my tivo) and Anton Blanchard hacked this into xine. I also
> have altivec-enabled motion compensation routines for libmpeg2.
>
> Hope this is useful...
Wow Paul, thanks! I adapted Apple's AltiVec IDCT from their tech library,
but anything I write using the C extensions is going to suck since
Motorola's GCC/binutils hack is useless. I never could get it to work (or
even compile). I'll try your version straight away!
-jwb
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-28 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 14:57 Call for help: altivec-enabled vlc Michel Lanners
2001-08-26 15:00 ` Michel Lanners
2001-08-26 16:39 ` Kaoru Fukui
2001-08-26 17:54 ` Michel Lanners
2001-08-26 21:21 ` Kaoru Fukui
2001-08-27 22:49 ` Michel Lanners
2001-08-28 12:32 ` Paul Mackerras
2001-08-28 14:19 ` Jeffrey W. Baker [this message]
2001-08-30 20:46 ` Michel Lanners
-- strict thread matches above, loose matches on Subject: below --
2001-08-29 6:02 Bill Fink
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=Pine.LNX.4.33.0108280718010.217-100000@desktop \
--to=jwbaker@acm.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=paulus@samba.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).