-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luc Verhaegen wrote:
On Fri, Mar 19, 2010 at 11:33:02AM -0700, Ian Romanick wrote:
I've been busy trying to get a release out the door, so I haven't looked
at these patches yet. I won't have a chance to look at the patches
until at least late
On Mon, Mar 22, 2010 at 2:24 AM, Luc Verhaegen l...@skynet.be wrote:
In
particular, the Mesa core - classic driver split only makes sense if
there are enough people who are actually working on those drivers who
would support the split. Otherwise, this is bound to lead straight
into hell.
In
On Mon, Mar 22, 2010 at 10:46:37PM +0100, Nicolai Haehnle wrote:
On Mon, Mar 22, 2010 at 2:24 AM, Luc Verhaegen l...@skynet.be wrote:
In
particular, the Mesa core - classic driver split only makes sense if
there are enough people who are actually working on those drivers who
would support
On Fri, Mar 19, 2010 at 06:26:03PM +0100, Nicolai Haehnle wrote:
On Thu, Mar 18, 2010 at 5:38 PM, Luc Verhaegen l...@skynet.be wrote:
So, identify the volatile interfaces, and the more stable interfaces,
and then isolate the volatile ones, and then you come to only one
conclusion.
Except
On Fri, Mar 19, 2010 at 12:44:39PM -0500, Bridgman, John wrote:
Pulling drm back out of the kernel tree seems like a hard sell, but the
ddx/mesa hw driver/libdrm set seemed like it might be a good candidate for
grouping.
I guess the core question is whether we expect the X-to-ddx and
On Fri, Mar 19, 2010 at 11:33:02AM -0700, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been busy trying to get a release out the door, so I haven't looked
at these patches yet. I won't have a chance to look at the patches
until at least late next week. I also
Nicolai Haehnle escribió:
because we want to
have the DRM in our codebase
Why?
--
__
| , , |
| / \ |
| ((__-^^-,-^^-__))
On Thu, Mar 18, 2010 at 5:38 PM, Luc Verhaegen l...@skynet.be wrote:
So, identify the volatile interfaces, and the more stable interfaces,
and then isolate the volatile ones, and then you come to only one
conclusion.
Except that the Mesa core - classic driver interface also wants to
change
Sent: Friday, March 19, 2010 1:26 PM
To: Luc Verhaegen
Cc: dri-devel@lists.sourceforge.net; mesa3d-...@lists.sourceforge.net;
x...@lists.freedesktop.org
Subject: Re: [Mesa3d-dev] DRI SDK and modularized drivers.
On Thu, Mar 18, 2010 at 5:38 PM, Luc Verhaegen l...@skynet.be wrote:
So, identify
On Wed, Mar 17, 2010 at 6:13 PM, Luc Verhaegen l...@skynet.be wrote:
On Wed, Mar 17, 2010 at 12:28:39AM +0100, Luc Verhaegen wrote:
Modularized dri drivers and an SDK enabled mesa tree are available in my
personal git repos at http://cgit.freedesktop.org/~libv/
The SDK enabled mesa tree adds
On Thu, Mar 18, 2010 at 01:28:28AM -0700, Corbin Simpson wrote:
On Wed, Mar 17, 2010 at 6:13 PM, Luc Verhaegen l...@skynet.be wrote:
On Wed, Mar 17, 2010 at 12:28:39AM +0100, Luc Verhaegen wrote:
Modularized dri drivers and an SDK enabled mesa tree are available in my
personal git repos at
On Wed, Mar 17, 2010 at 12:28:39AM +0100, Luc Verhaegen wrote:
Modularized dri drivers and an SDK enabled mesa tree are available in my
personal git repos at http://cgit.freedesktop.org/~libv/
The SDK enabled mesa tree adds to the mesa build system to create shared
libraries libmesadri and
12 matches
Mail list logo
