On Tue, Jun 12, 2012 at 7:34 PM, Martin Langhoff martin@laptop.org wrote:
On Tue, Jun 12, 2012 at 1:04 PM, Peter Robinson pbrobinson@gmail.com wrote:
I was just going on the logs from git and we have 2.0.13 and according to the logs 2.0.13 was post that commit, but it seems it wasn't tagged so I assume 2.0.13 is the same as 2.0.12 then
I think you have some other commit in mind. From 2.0.12 to 2.0.13 you have one commit that enables render accel, that is in xorg.conf. That's not what we were after, we were after a udev rule that allows talking to the device nodes that the vmeta implementation exposes.
No problem. Just material for the next build ;-)
Speaking of next builds, is there an ETA?
-Jon
On Tue, Jun 12, 2012 at 6:48 PM, Jon Nettleton jon.nettleton@gmail.com wrote:
On Tue, Jun 12, 2012 at 7:34 PM, Martin Langhoff martin@laptop.org wrote:
On Tue, Jun 12, 2012 at 1:04 PM, Peter Robinson pbrobinson@gmail.com wrote:
I was just going on the logs from git and we have 2.0.13 and according to the logs 2.0.13 was post that commit, but it seems it wasn't tagged so I assume 2.0.13 is the same as 2.0.12 then
I think you have some other commit in mind. From 2.0.12 to 2.0.13 you have one commit that enables render accel, that is in xorg.conf. That's not what we were after, we were after a udev rule that allows talking to the device nodes that the vmeta implementation exposes.
No problem. Just material for the next build ;-)
Speaking of next builds, is there an ETA?
was waiting for the fix for 11923.
Peter
-
Jon Nettleton -
Peter Robinson