[Bug 2497] r200 dri driver: glut menues are broken in sw-tnl mode

2005-07-03 Thread bugzilla-daemon
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=2497 [EMAIL PROTECTED] changed: What|Removed |Added

Re: DRI vs DRM

2005-07-03 Thread Alan Cox
On Sul, 2005-07-03 at 05:04, Jon Smirl wrote: There are three DRI drivers with no DRM. What is up with these? gamma s3v trident trident was never finished s3v and gamma were both against old DRM and are not shipped in curren trees ---

Re: DRI vs DRM

2005-07-03 Thread Jon Smirl
Any ideas on what to call my DRM sysfs attribute which provides the name of the corresponding DRI library? I named it dri initially but that may not be descriptive enough. -- Jon Smirl [EMAIL PROTECTED] --- SF.Net email is sponsored by:

Re: DRI vs DRM

2005-07-03 Thread Jon Smirl
On 7/3/05, Adam Jackson [EMAIL PROTECTED] wrote: Shouldn't this just be a string you pull right out of a drm ioctl? I know the name currently lives in the server, but as with many things the server does I think that's a mistake. Binding EGL driver load to sysfs is not portable. The code is

Re: DRI vs DRM

2005-07-03 Thread Jon Smirl
On 7/3/05, Jon Smirl [EMAIL PROTECTED] wrote: Any ideas on what to call my DRM sysfs attribute which provides the name of the corresponding DRI library? I named it dri initially but that may not be descriptive enough. I called it dri_library_name, we can always change it. -- Jon Smirl [EMAIL

Re: DRI vs DRM

2005-07-03 Thread Adam Jackson
On Sunday 03 July 2005 12:31, Jon Smirl wrote: On 7/3/05, Adam Jackson [EMAIL PROTECTED] wrote: Shouldn't this just be a string you pull right out of a drm ioctl? I know the name currently lives in the server, but as with many things the server does I think that's a mistake. Binding

Re: DRI vs DRM

2005-07-03 Thread Jon Smirl
On 7/3/05, Adam Jackson [EMAIL PROTECTED] wrote: Why aren't the DRI drivers themselves EGL drivers? That's sort of the model I was anticipating: - eglChooseDisplayMESA(display/0) - EGL translates to /dev/dri/card0, opens it - ioctl: what's the DRI driver name for this device? - kernel:

Re: DRI vs DRM

2005-07-03 Thread Brian Paul
Jon Smirl wrote: On 7/3/05, Adam Jackson [EMAIL PROTECTED] wrote: Why aren't the DRI drivers themselves EGL drivers? That's sort of the model I was anticipating: - eglChooseDisplayMESA(display/0) - EGL translates to /dev/dri/card0, opens it - ioctl: what's the DRI driver name for this

Re: DRI vs DRM

2005-07-03 Thread Adam Jackson
On Sunday 03 July 2005 18:40, Brian Paul wrote: I said I'd like to keep the src/egl/main/ directory cross-platform. The Linux version of libEGL.so could certainly have additional code in it. But I'm certainly open to ideas. I just don't have much time to spend on this project. I'm still not

Re: DRI vs DRM

2005-07-03 Thread Matthew Tippett
Title: Re: DRI vs DRM There is a standard name the library. See Section 8.2 - Packaging/Libraries of the OpenGL|ES spec on Khronos' web page. It should be libGLES_xx.so where xx is CM or CL. Regards... Matthew -- Blackberry-Sent Matthew Tippett Acting Engineering Manager, Linux

Re: DRI vs DRM

2005-07-03 Thread Jon Smirl
On 7/3/05, Brian Paul [EMAIL PROTECTED] wrote: I said I'd like to keep the src/egl/main/ directory cross-platform. The Linux version of libEGL.so could certainly have additional code in it. But I'm certainly open to ideas. I just don't have much time to spend on this project. The code is in

[2.6 patch] DRM: misc cleanup

2005-07-03 Thread Adrian Bunk
I've seen that part of this is already in recent kernels. Below is as a FYI a version against 2.6.13-rc1-mm1. -- snip -- This patch contains the following cleanups: - make needlessly global functions static - remove the following unused global functions: - drm_fops.c: drm_read -

Re: Where/how to start implementing vertical retrace interrupt interface?

2005-07-03 Thread Will Dyson
On 7/2/05, Peter Ronnquist [EMAIL PROTECTED] wrote: I've added the dri-devel and xorg mailing lists to the cc: list. If I have understood things correctly then X/x.org can not provide a flicker free update of the graphics on a display since the linux kernel does not provide a way to

Re: DRM map design

2005-07-03 Thread Paul Mackerras
Keith Whitwell writes: Sounds good Paul. I think it's worthwhile to at least investigate this as it'd be a cleaner result all round at the end. Based on Egbert's comments about the use of an idr structure restricting our choice of token values, I have taken an alternative approach where I

Re: DRM map design

2005-07-03 Thread Paul Mackerras
Jon Smirl writes: drmMap never cares about the handle since drmMap turns into mmap and mmap doesn't know about DRM maps. Huh? drm_mmap certainly does know about DRM maps. The trouble with using the offset returned by drmGetMap is that if your program is a 32-bit program running on a 64-bit

Re: DRM map design

2005-07-03 Thread Jon Smirl
On 7/3/05, Paul Mackerras [EMAIL PROTECTED] wrote: Jon Smirl writes: drmMap never cares about the handle since drmMap turns into mmap and mmap doesn't know about DRM maps. Huh? drm_mmap certainly does know about DRM maps. I see now that drmMap is overriding mmap's offset to pass in the