From: Ian Romanick <idr@freedesktop.org>
To: Luc Verhaegen <libv@skynet.be>
Cc: dri-devel@lists.sourceforge.net,
mesa3d-dev@lists.sourceforge.net, xorg@lists.freedesktop.org
Subject: Re: [Mesa3d-dev] DRI SDK and modularized drivers.
Date: Mon, 22 Mar 2010 10:41:18 -0700 [thread overview]
Message-ID: <4BA7ABBE.6080000@freedesktop.org> (raw)
In-Reply-To: <20100322015442.GC8768@skynet.be>
-----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 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, and I think this is significant, is that the
functionality provided by the xf86 video drivers through the X server
hasn't changed much in quite some time. The amount of functionality
added in every single major release of Mesa which requires driver
changes is significant. We're far enough behind the state of the GL
spec and the closed-source drivers that I don't really want anything
that will slow us down.
You can't aim a stable interface at a moving target.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkunq7sACgkQX1gOwKyEAw8dqwCfR9/JjfCecV0Q4Po4AdnJaTOE
QrQAoJu1+zMz5shOHrhmOSL+L2um190q
=+eep
-----END PGP SIGNATURE-----
_______________________________________________
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
next prev parent reply other threads:[~2010-03-22 17:41 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
2010-03-22 17:41 ` Ian Romanick [this message]
2010-03-19 23:28 ` [Mesa3d-dev] " 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=4BA7ABBE.6080000@freedesktop.org \
--to=idr@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=libv@skynet.be \
--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.