From: Dave Airlie <airlied@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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: Sat, 16 Apr 2005 02:06:38 +1000 [thread overview]
Message-ID: <21d7e9970504150906e821374@mail.gmail.com> (raw)
In-Reply-To: <1113577241.11155.21.camel@localhost.localdomain>
On 4/16/05, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mer, 2005-04-13 at 14:23, Lennart Sorensen wrote:
> > On Wed, Apr 13, 2005 at 03:06:46PM +0200, Lars Marowsky-Bree wrote:
> > Graphics card companies don't realize they are hardware companies not
> > software companies and that it is hardware they make their money from?
> > Oh and they have too many lawyers?
>
> Actually they are both. 3D performance is a combination of clever driver
> technology -and- clever hardware.
Not to disagree too much, most of those "clever" driver technologies
are dirty hacks that boost performance in the quake/doom3 type
cases... but if they ever open sourced it those hardware review sites
would be over them like a bad rash...
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...
Dave.
next prev parent reply other threads:[~2005-04-15 16:06 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 [this message]
2005-04-15 16:19 ` Duncan Sands
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=21d7e9970504150906e821374@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox