linux-kernel - Re: Radeon KMS status (Re: [git pull] drm radeon kms.)

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]

Date:	Wed, 11 Nov 2009 09:14:31 +0000 (GMT)
From:	Dave Airlie <airlied@...ux.ie>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	dri-devel@...ts.sf.net, glisse@...edesktop.org
Subject: Re: Radeon KMS status (Re: [git pull] drm radeon kms.)

> Hi Dave,
> 
> I was wondering about the current state of Radeon KMS, how far are we
> from having it removed from staging?

I'm sort of thinking the next merge window of moving the enable option 
into the kernel proper. We still have a metric shitload of work to get to 
feature parity with current userspace drivers and we've done no 
optimisation work on the rendering portion of the stack so I'm not sure 
freezing the API isn't a bit premature, however maybe the API we have is 
good enough to support and we can add new ioctls to make it go faster if 
we require.

Jerome has proposed some API changes but we really haven't had time to 
validate them in any useful way.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/