On Tue, 12 May 2009 15:19:34 -0700
Andrew Morton a...@linux-foundation.org wrote:
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 12 May 2009 01:40:48 GMT
bugzilla-dae...@bugzilla.kernel.org wrote:
On my system, the colors
I submitted a patch for the below error a while back... this problem is still
present in 2.6.30-rc5. Am I submitting this patch to the right place??? If
not, where should I send it?
Sorry for troubling you. Thanks in advance,
Jonas
Jonas Bonn wrote:
With 2.6.30-rc4 I get the following
Bridgman, John wrote:
My understanding was that XF86DRIQueryDirectRenderingCapable just asked
the X server if *it* was able to support direct rendering on a
particular screen, didn't tell you anything about whether the right 3D
driver existed or was installed correctly.
That would explain to
On Thu, 2009-05-14 at 10:35 +0200, Enno Fennema wrote:
Now, if I may, back to my immediate problem.
It might have been a good idea to start with that in the first place. :)
I have a program that runs perfectly when passing False as 4th
argument to glXCreateContext. glXIsDirect confirms I
http://bugs.freedesktop.org/show_bug.cgi?id=21582
--- Comment #4 from Maciej Cencora m.cenc...@gmail.com 2009-05-14 05:31:04
PST ---
The problem is in radeonRefillCurrentDmaRegion:
we call radeon_revalidate_bos which calls radeonFlush which frees
rmesa-dma.current (only if some conditions
Michel Dänzer wrote:
It depends on the arguments to glXMakeCurrent. E.g. if the drawable is a
pixmap, that isn't supported without DRI2.
Good to get on a sidetrack again. You are right. XF86 does appear not to
support rendering to GLXPixmaps with a direct context.
But I was using an
Just to add to my mail of a few minutes ago. I had a look at the GLX 1.4
manual and glXMakeCurrent should never return a BadValue error.
I am even more foxed
Enno
--
The NEW KODAK i700 Series Scanners deliver under
On Thu, 14 May 2009 09:47:38 +0200
Jonas Bonn jo...@southpole.se wrote:
I submitted a patch for the below error a while back... this problem
is still present in 2.6.30-rc5. Am I submitting this patch to the
right place??? If not, where should I send it?
Sorry for troubling you. Thanks in
http://bugs.freedesktop.org/show_bug.cgi?id=21609
--- Comment #3 from Paulo Dias paulo_c_d...@ig.com.br 2009-05-14 10:25:19
PST ---
does this bug fixed the rgba problem with dri2 and kde4/compiz/gtk? because i'm
using the latest mesa from glisse (which has this patch) and i'm still having
On Tue, 2009-05-05 at 10:00 -0400, Jarod Wilson wrote:
There are a number of small form factor desktop systems with Intel mobile
graphics chips that lie and say they have an LVDS. With kernel mode-setting,
this becomes a problem, and makes native resolution boot go haywire -- for
example, my
From: Kristian Høgsberg k...@redhat.com
This patch adds a vblank synced pageflip ioctl for to the modesetting
family of ioctls. The ioctl takes a crtc and an fb and schedules a
pageflip to the new fb at the next coming vertical blank event. This
feature lets userspace implement tear-free
On Fri, 2009-05-15 at 14:46 +1000, Benjamin Herrenschmidt wrote:
Hi Jesse !
Haven't had much time to investigate the problem I've been talking to
you and David about but from what I can see in the code, we're probably
hitting this in drm_mmap_locked() in drm_vm.c :
/* Check for
Hi Jesse !
Haven't had much time to investigate the problem I've been talking to
you and David about but from what I can see in the code, we're probably
hitting this in drm_mmap_locked() in drm_vm.c :
/* Check for valid size. */
if (map-size vma-vm_end - vma-vm_start)
13 matches
Mail list logo
