From: Luc Verhaegen <libv@skynet.be>
To: Ian Romanick <idr@freedesktop.org>
Cc: dri-devel@lists.sourceforge.net, xorg@lists.freedesktop.org,
mesa3d-dev@lists.sourceforge.net
Subject: Re: DRI SDK and modularized drivers.
Date: Mon, 22 Mar 2010 02:54:42 +0100 [thread overview]
Message-ID: <20100322015442.GC8768@skynet.be> (raw)
In-Reply-To: <4BA3C35E.4050200@freedesktop.org>
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 wasn't at FOSDEM, so I don't have
> any of the background info.
I've grouped the slides and the recordings at the top of my blog entry
about this.
The patches themselves are actually copies of eachother, with minor
differences to adjust for changes of the tree around it (there are 16 or
so versions of the sdk done from 7.0 through 7.8). Any actual patch is
small, and it is build system only.
> If these patches try to enforce a "stable" interface between core Mesa
> and the classic DRI drivers, we're not interested. At all. This has
> been discussed and rejected many, many times before.
Ah, prepossession.
Ask yourself, did the fact that xf86 video drivers were out of tree,
ever stop anyone from _really_ bad api breakage stunts?
The difference with in-tree and out-of-tree here is that out-of-tree
should, theoretically, lead to more prudent interface changes. This
without having to enforce anything, it happens naturally.
Out of tree drivers never stop interface changes, they just make them a
tiny bit more involved, and therefor, hopefully, causes the person
making those changes to consider his actions a bit better.
But as said in an earlier email, what you incur on overhead here you
can easily make up in the driver internal interfaces. And then the other
synergies come weighing in.
Luc Verhaegen.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next prev parent reply other threads:[~2010-03-22 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100316232839.GA27423@skynet.be>
2010-03-18 1:13 ` [Mesa3d-dev] DRI SDK and modularized drivers Luc Verhaegen
2010-03-18 8:28 ` Corbin Simpson
2010-03-18 16:38 ` Luc Verhaegen
2010-03-19 17:26 ` Nicolai Haehnle
2010-03-19 17:44 ` Bridgman, John
2010-03-19 18:22 ` Luca Barbieri
2010-03-22 1:37 ` Luc Verhaegen
2010-03-19 18:33 ` [Mesa3d-dev] " Ian Romanick
2010-03-22 1:54 ` Luc Verhaegen [this message]
2010-03-22 17:41 ` Ian Romanick
2010-03-19 23:28 ` Octavio Rossell
2010-03-22 1:24 ` Luc Verhaegen
2010-03-22 21:46 ` Nicolai Haehnle
2010-03-22 23:49 ` [Mesa3d-dev] " Luc Verhaegen
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=20100322015442.GC8768@skynet.be \
--to=libv@skynet.be \
--cc=dri-devel@lists.sourceforge.net \
--cc=idr@freedesktop.org \
--cc=mesa3d-dev@lists.sourceforge.net \
--cc=xorg@lists.freedesktop.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 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.