On Fri, Mar 5, 2010 at 2:23 AM, Dave Airlie airl...@gmail.com wrote:
So with all this ongoing Linus crap I'm going to be brave and ask for
reasons why
0.0.16 kernel API can't become 1.0.0.
Pros:
All old userspace compatibility is gone.
No more UMS cruft to support.
Something can be shipped
Another possible reason for breaking ABI that hasn't yet been
mentioned is the fact that right now any DRM client can trivially lock
up the GPU and/or corrupt GPU/GART memory belonging to other clients.
This happens often with GL driver bugs and is quite annoying for
developers and testers of
http://bugs.freedesktop.org/show_bug.cgi?id=26906
--- Comment #1 from Francisco Jerez curroje...@riseup.net 2010-03-05
05:11:13 PST ---
(In reply to comment #0)
By default, I get 6-bit color depth on my laptop. To get full 8-bit color
depth
on, I have to run the following command to
http://bugs.freedesktop.org/show_bug.cgi?id=26797
--- Comment #6 from Frank Schaefer fschaefer@googlemail.com 2010-03-05
05:56:07 PST ---
Created an attachment (id=33788)
-- (http://bugs.freedesktop.org/attachment.cgi?id=33788)
First 100MB of the vb-trace
--
Configure bugmail:
http://bugs.freedesktop.org/show_bug.cgi?id=26797
--- Comment #7 from Frank Schaefer fschaefer@googlemail.com 2010-03-05
06:01:33 PST ---
LZMA compresses the whole 2 GB to 14.1 MB (!).
So I could send it, too.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
http://bugs.freedesktop.org/show_bug.cgi?id=26797
--- Comment #8 from Francisco Jerez curroje...@riseup.net 2010-03-05
06:14:40 PST ---
(In reply to comment #7)
LZMA compresses the whole 2 GB to 14.1 MB (!).
So I could send it, too.
It would be interesting as well. Thanks.
--
http://bugs.freedesktop.org/show_bug.cgi?id=26797
--- Comment #10 from Francisco Jerez curroje...@riseup.net 2010-03-05
06:34:46 PST ---
(In reply to comment #9)
As attachment or per mail (like the mmiotrace) ?
Per mail, preferably to the mmio.dumps account.
--
Configure bugmail:
On Thu, Mar 4, 2010 at 8:23 PM, Dave Airlie airl...@gmail.com wrote:
So with all this ongoing Linus crap I'm going to be brave and ask for
reasons why
0.0.16 kernel API can't become 1.0.0.
Pros:
All old userspace compatibility is gone.
No more UMS cruft to support.
Something can be shipped
So, after discussion on irc, here is an idea/proposal.
We could flag the upcoming couple of months (two months sounds like
enough?) as the nouveau DRM stabilizing timeframe. Everything that
we think should go into the DRM (basically everything which we want to
go in and can be achieved in that
