public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Dave Airlie <airlied@linux.ie>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.sf.net, glisse@freedesktop.org
Subject: Re: Radeon KMS status (Re: [git pull] drm radeon kms.)
Date: Wed, 11 Nov 2009 10:33:48 +0100	[thread overview]
Message-ID: <1257932028.23203.74.camel@twins> (raw)
In-Reply-To: <alpine.DEB.2.00.0911110910170.4943@skynet.skynet.ie>

On Wed, 2009-11-11 at 09:14 +0000, Dave Airlie wrote:
> > 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.

I by no means intend to rush things along, so if you think you need more
time, please take it ;-)

Just wanted to know where we stand... I'll try the Radeon KMS thing
again once I get through this mountain of email that accumulated over
the vacation and let you know how the current bits work.

Last time I tried KMS swapped the two DVI outputs wrt. the !KMS setup,
which is rather annoying during the transition period, but nothing I
can't live with once the stuff is stable enough to use all day.

  reply	other threads:[~2009-11-11  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 23:14 [git pull] drm radeon kms Dave Airlie
2009-11-11  8:01 ` Radeon KMS status (Re: [git pull] drm radeon kms.) Peter Zijlstra
2009-11-11  9:14   ` Dave Airlie
2009-11-11  9:33     ` Peter Zijlstra [this message]
2009-11-11  9:36       ` Dave Airlie

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=1257932028.23203.74.camel@twins \
    --to=peterz@infradead.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=glisse@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox