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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 11 Nov 2009 09:36:59 +0000 (GMT)
From:	Dave Airlie <>
To:	Peter Zijlstra <>
Subject: Re: Radeon KMS status (Re: [git pull] drm radeon kms.)

> > 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.

The easiest way to test it jsut grab an F12 LiveCD

Its pretty much got what I've just asked Linus to pull, and won't ruin 
your already installed system, handy for testing s/r if ppl use it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists