From: Duncan Sands <baldrick@free.fr>
To: Dave Airlie <airlied@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Lars Marowsky-Bree <lmb@suse.de>,
Helge Hafting <helge.hafting@aitel.hist.no>,
John M Collins <jmc@xisl.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Exploit in 2.6 kernels
Date: Fri, 15 Apr 2005 18:19:28 +0200 [thread overview]
Message-ID: <1113581968.22320.20.camel@localhost.localdomain> (raw)
In-Reply-To: <21d7e9970504150906e821374@mail.gmail.com>
> I still don't think they would lose out by much.. I've just being
> trying to RE the ATI Mpeg2 IDCT/MC hardware, ATI know this, I know
> this, they are only wasting my time and my employers money (we still
> are going to buy their chips... no choice..) will they give out specs
> .. no .. why? cause of lawyers.. they use MPEG2 decoders for DVD
> decode and some lawyer told them this is a major secret despite the
> fact that everyone knows how to decode Mpeg2 and DVDs at this stage..
>
> same story with VIA who persist on giving out a binary only blob for
> MPEG2 hardware despite the fact that it was RE'ed over two years ago..
> the secret is out...
When I was RE the ATI IDCT stuff a few years ago, someone at ATI told
me that the problem was that the company they licensed the IDCT stuff
from wouldn't let them give out any specs. I may be remembering this
wrong since it was a long time ago...
Duncan.
PS: At some point I changed hardware, and didn't need the IDCT anymore.
I just tried to find my notes on it, but there only seems to be some
stuff about the tv tuner...
next prev parent reply other threads:[~2005-04-15 16:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 9:34 Exploit in 2.6 kernels John M Collins
2005-04-12 12:24 ` Baruch Even
2005-04-12 15:00 ` John M Collins
2005-04-12 21:08 ` Chris Wright
2005-04-12 21:32 ` John M Collins
2005-04-13 5:28 ` Valdis.Kletnieks
2005-04-13 9:47 ` Helge Hafting
2005-04-13 12:59 ` Lennart Sorensen
2005-04-13 13:06 ` Lars Marowsky-Bree
2005-04-13 13:23 ` Lennart Sorensen
2005-04-13 14:01 ` John M Collins
2005-04-16 2:32 ` Adrian Bunk
2005-04-13 15:22 ` Chris Friesen
2005-04-14 14:01 ` Helge Hafting
2005-04-20 18:17 ` nVidia stuff again Doug Ledford
2005-04-20 23:12 ` Dave Airlie
2005-04-21 11:23 ` Helge Hafting
2005-04-21 12:15 ` Doug Ledford
2005-04-21 12:54 ` Dave Airlie
2005-04-21 13:35 ` Lennart Sorensen
2005-04-21 14:43 ` Manu Abraham
2005-04-21 21:17 ` J.A. Magallon
2005-04-22 14:44 ` Arjan van de Ven
2005-04-15 15:00 ` Exploit in 2.6 kernels Alan Cox
2005-04-15 16:06 ` Dave Airlie
2005-04-15 16:19 ` Duncan Sands [this message]
2005-04-14 12:46 ` Helge Hafting
2005-05-05 22:00 ` Olaf Titz
2005-04-13 13:02 ` Lennart Sorensen
2005-04-13 14:26 ` Eric Rannaud
2005-04-13 14:41 ` Lennart Sorensen
2005-04-14 20:02 ` Greg Folkert
2005-04-14 22:27 ` John M Collins
2005-05-09 18:37 ` Alessandro Salvatori
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=1113581968.22320.20.camel@localhost.localdomain \
--to=baldrick@free.fr \
--cc=airlied@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=helge.hafting@aitel.hist.no \
--cc=jmc@xisl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=lsorense@csclub.uwaterloo.ca \
/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.