https://bugs.freedesktop.org/show_bug.cgi?id=63714
Christian K?nig changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Christian K
https://bugs.freedesktop.org/show_bug.cgi?id=63714
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Christian K
https://bugs.freedesktop.org/show_bug.cgi?id=63714
--- Comment #3 from ryszardzonk at yahoo.com ---
yes it in did seems like a coding frenzy took place in recent days ;). using
kernel 3.9.0-rc7 and applying around ~50 newest patches from
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.1
https://bugs.freedesktop.org/show_bug.cgi?id=63714
--- Comment #3 from ryszardz...@yahoo.com ---
yes it in did seems like a coding frenzy took place in recent days ;). using
kernel 3.9.0-rc7 and applying around ~50 newest patches from
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.10 t
https://bugs.freedesktop.org/show_bug.cgi?id=63714
Christian K?nig changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=63714
--- Comment #1 from Alex Deucher ---
You are probably using an old set of kernel patches. There were several
revisions. The mesa code checks to see if the kernel is new enough and the
latest kernel patch revision bumps the kernel driver version
https://bugs.freedesktop.org/show_bug.cgi?id=63714
Christian König changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=63714
--- Comment #1 from Alex Deucher ---
You are probably using an old set of kernel patches. There were several
revisions. The mesa code checks to see if the kernel is new enough and the
latest kernel patch revision bumps the kernel driver version