lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1218077846.24714.290.camel@koto.keithp.com>
Date:	Wed, 06 Aug 2008 19:57:26 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Stephane Marchesin <marchesin@...s.u-strasbg.fr>
Cc:	keithp@...thp.com, Arjan van de Ven <arjan@...radead.org>,
	John Stoffel <john@...ffel.org>,
	Hugh Dickins <hugh@...itas.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Christoph Hellwig <hch@...radead.org>,
	Eric Anholt <eric@...olt.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Export shmem_file_setup and shmem_getpage for DRM-GEM

On Thu, 2008-08-07 at 04:16 +0200, Stephane Marchesin wrote:

> Btw, I was wondering what prevented you (you being the intel people)
> from fixing TTM instead of writing GEM ? That's what happened, there
> was TTM first, intel came first, they should've fixed it...

Well, we (mostly Eric, but a bit of work by me as well) spent about a
year trying to fix it, with Thomas' help, but after that, we still
hadn't managed to make the 965 run OpenGL reasonably well.

Around April 1, we (Eric and I) evaluated how long it would take to
built just what we needed, rather than trying to work out a general
architecture that could serve every hardware need we could think of. We
figured it would take about a month to get something working, and by the
end of April, we had 3D working better on 965 than we had ever managed
with TTM.

Given the difficulty we had understanding the TTM internals, it's
possible that this was just a failure on our part. But as we expect a
wide range of people to maintain this code going forward, it seemed
reasonable to want something simple enough that even we could figure out
how it works.

I think TTM is over designed, but that is colored by experience with
very simple hardware. While I think something simple, like GEM, could
work on most hardware, I really don't know and invite you to try
whatever approach you want.

Also, we're talking about moving code into the Linux kernel source tree
to support Intel integrated graphics. There is no incumbent
implementation there that we're trying to replace, this is new
functionality for Linux.

-- 
keith.packard@...el.com

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ