Need sample program or tutorial
In the absence of much activity on the user list I come for assistance here, I fail miserably in my first attempt to write a direct rendering client. I think DRI is properly installed on my system, at least glxinfo confirms Direct rendering: Yes. As a first step I just want to draw a trangle in a window. My program initializes all kind of things but when it comes to make something current I get probably confused between all contexts and windows/drawables or missed some vital step. Is there anywhere a tutorial that tells me how to write a DRI client program (not how to compile and install DRI) or a very simple program that I could have a look at. Appreciate any pointers. Enno Fennema -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Need sample program or tutorial
On Wed, 2009-05-13 at 10:00 +0200, Enno Fennema wrote: In the absence of much activity on the user list I come for assistance here, I fail miserably in my first attempt to write a direct rendering client. I think DRI is properly installed on my system, at least glxinfo confirms Direct rendering: Yes. As a first step I just want to draw a trangle in a window. My program initializes all kind of things but when it comes to make something current I get probably confused between all contexts and windows/drawables or missed some vital step. Is there anywhere a tutorial that tells me how to write a DRI client program (not how to compile and install DRI) or a very simple program that I could have a look at. Appreciate any pointers. Enno Fennema DRI is a protocol which is here to allow X GL client to directly talk with GL driver and GL driver to talk with X to know where to render. It's not intended to be used by anyone else beyond GL driver or X server. What you want is simply a GL application and there is tons of example out there on how to do one, you could also find examples in mesa/progs/* mese/progs/trivial/tri-* for instance show how to render a simple triangle. So GL app will talk to GL driver which will use DRI on your computer if it's enabled. Cheers, Jerome Glisse -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 13294] New: i915: drm: xorg leaks drm objects massively
http://bugzilla.kernel.org/show_bug.cgi?id=13294
Summary: i915: drm: xorg leaks drm objects massively
Product: Drivers
Version: 2.5
Kernel Version: 2.6.30-rc4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI)
AssignedTo: drivers_video-...@kernel-bugs.osdl.org
ReportedBy: r...@sisk.pl
Blocks: 13070
Regression: Yes
Subject: [BUG] i915: drm: xorg leaks drm objects massively:
linux-2.6.30-rc{4,5}
Submitter : Sergei Trofimovich sly...@gmail.com
Date : 2009-05-10 19:56
References : http://marc.info/?l=linux-kernelm=124198547027903w=4
This entry is being used for tracking a regression from 2.6.29. Please don't
close it until the problem is fixed in the mainline.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 20954] mesa/drm(git): kernel panic with radeon driver (Radeon 9500 Pro)
http://bugs.freedesktop.org/show_bug.cgi?id=20954 --- Comment #7 from Rafael Antonio Porras Samaniego sp...@distrobit.net 2009-05-13 05:49:17 PST --- (In reply to comment #6) Many more reports: https://bugs.gentoo.org/show_bug.cgi?id=264280 This still exists in latest kernel src and drm git. Rafael, are you going to submit for inclusion? How? I thought that filing a bug report was the way to fix this issue. Dug around in the source to try and confirm the fix, but I can't find the code that would ever make this mmio pointer be NULL. I wonder if we are operating on this structure after it has been freed? Or am I missing something? I reviewed the code and also I was unable to find the sentence that turns NULL the pointer. To be honest, I don't see my patch as a fix because it attacks the symptom and not the illness. I'll try again to find the point where dev_priv-mmio is nullified but I'm afraid that I won't get anything useful. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[git pull] drm fix
The following changes since commit 8c9ed899b44c19e81859fbb0e9d659fe2f8630fc: David Howells (1): NOMMU: Don't check vm_region::vm_start is page aligned in add_nommu_region() are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-2.6 for-linus Jesse Barnes (1): drm/i915: automatically select FRAMEBUFFER_CONSOLE if !EMBEDDED drivers/gpu/drm/Kconfig |1 + 1 files changed, 1 insertions(+), 0 deletions(-) Just one fix so far for a common complaint. I think Ben has an important fix on the way soon too, but I haven't received it yet and didn't want to lose this one. Thanks, -- Jesse Barnes, Intel Open Source Technology Center -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: Need sample program or tutorial
Couldn't DRI also be used by a non-GL direct-rendering driver, eg. for something like video acceleration ? -Original Message- From: Jerome Glisse [mailto:gli...@freedesktop.org] Sent: Wednesday, May 13, 2009 4:53 AM To: Enno Fennema Cc: dri-devel@lists.sourceforge.net Subject: Re: Need sample program or tutorial On Wed, 2009-05-13 at 10:00 +0200, Enno Fennema wrote: In the absence of much activity on the user list I come for assistance here, I fail miserably in my first attempt to write a direct rendering client. I think DRI is properly installed on my system, at least glxinfo confirms Direct rendering: Yes. As a first step I just want to draw a trangle in a window. My program initializes all kind of things but when it comes to make something current I get probably confused between all contexts and windows/drawables or missed some vital step. Is there anywhere a tutorial that tells me how to write a DRI client program (not how to compile and install DRI) or a very simple program that I could have a look at. Appreciate any pointers. Enno Fennema DRI is a protocol which is here to allow X GL client to directly talk with GL driver and GL driver to talk with X to know where to render. It's not intended to be used by anyone else beyond GL driver or X server. What you want is simply a GL application and there is tons of example out there on how to do one, you could also find examples in mesa/progs/* mese/progs/trivial/tri-* for instance show how to render a simple triangle. So GL app will talk to GL driver which will use DRI on your computer if it's enabled. Cheers, Jerome Glisse -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Need sample program or tutorial
Jerome Glisse wrote: ... Why do you want to use XF86DRIQueryDirectRenderingCapable ? I only called XF86...Capable to confirm that the software recognized my video card as *capable* of direct rendering. glXIsDirect tells you what you want to know ie if it's direct or not. Correct, glXDirect tells me the context is or is not *using* direct rendering. I don't understand what you are trying to do here, you shouldn't care to know if direct rendering is enabled or not, applications shouldn't behave differently if DRI is enabled or not. I thought direct rendering is faster than indirect as it avoids the translation from OpenGL to the X protocol and then back again. The difference in application behaviour is then only speed but it my case the difference is 'crash' or 'works ok'. Another question is why should I specify direct/indirect in glXCreateContext if there is no reason to care. My longer term aim is to understand what my Radeon SE9200 can and cannot do. Mesa is so clever that it hides by software when hardware is deficient. I think that only by getting access to the the drm kernel driver can I start exploring the hardware. As John Bridgman wrote DRI might be useful too for non-GL applications, which do want contact with the X server not to clobber other windows but otherwise would like to access non-GL capabilities of the hardware or GL capabilities in a differnt way. Radeon documentation is possibly available but under non disclosure conditions which I do not want to accept. At least I found very little publicly available. In the short run I try to understand a bit better how DRI manages the relation ships between X windows, those that GLXWindows and, maybe an impossible animal, a DRM Window, which shows consideration for other X windows. Regards, Enno -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Need sample program or tutorial
Enno Fennema wrote: My longer term aim is to understand what my Radeon SE9200 can and cannot do. Mesa is so clever that it hides by software when hardware is deficient. I think that only by getting access to the the drm kernel driver can I start exploring the hardware. The DRM only exposes a few simple ioctls; the actual acceleration is done in Mesa. You'll need to read through the Mesa r200 code to understand what your card can and cannot do. :3 As John Bridgman wrote DRI might be useful too for non-GL applications, which do want contact with the X server not to clobber other windows but otherwise would like to access non-GL capabilities of the hardware or GL capabilities in a differnt way. That sounds icky. We're already working on a project called Gallium3D, which allows us to write non-GL apps in a standardized, simple way. (Of course, unfortunately, r200 isn't planned as part of Gallium3D... :C ) Radeon documentation is possibly available but under non disclosure conditions which I do not want to accept. At least I found very little publicly available. r200 is documented in code; check out the r200-specific parts of xf86-video-ati and Mesa for more info. In the short run I try to understand a bit better how DRI manages the relation ships between X windows, those that GLXWindows and, maybe an impossible animal, a DRM Window, which shows consideration for other X windows. It's already been done with cairo-drm, which created Cairo contexts directly bound to i915 hardware through DRM. So it's certainly possible. ~ C. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: Need sample program or tutorial
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. I think the convention is to ask for direct when creating a context unless you have a good reason for needing indirect (eg some compositing managers need to use indirect), then if you care you can use glXIsDirect to see if you got it. The DRI API is for inter-driver communication only AFAIK, not for application use. Not sure what hardware documentation has to do with this; pretty much everything in the original R200 documentation (I'm guessing that's what you're referring to, since there is a lot of publicly available documentation for newer chips) has been transcribed into the open source drivers already. In terms of the relationship, I thought it was basically : - app calls GL lib - GL lib uses DRI to see if server supports direct rendering for that screen - if yes, GL lib makes other calls to set up shared areas and find name of 3d driver - if all that succeeds, GL lib passes drawing calls directly to the 3d driver AIGLX is more complicated but not a lot more so. Anyways, bottom line is that if you are writing another direct rendering driver you probably should be using DRI calls and if you are not writing a driver then you probably should just be using GLX calls... or something like that ;) -Original Message- From: Enno Fennema [mailto:e.fenn...@tiscali.nl] Sent: Wednesday, May 13, 2009 3:57 PM To: Jerome Glisse; Bridgman, John Cc: dri-devel@lists.sourceforge.net Subject: Re: Need sample program or tutorial Jerome Glisse wrote: ... Why do you want to use XF86DRIQueryDirectRenderingCapable ? I only called XF86...Capable to confirm that the software recognized my video card as *capable* of direct rendering. glXIsDirect tells you what you want to know ie if it's direct or not. Correct, glXDirect tells me the context is or is not *using* direct rendering. I don't understand what you are trying to do here, you shouldn't care to know if direct rendering is enabled or not, applications shouldn't behave differently if DRI is enabled or not. I thought direct rendering is faster than indirect as it avoids the translation from OpenGL to the X protocol and then back again. The difference in application behaviour is then only speed but it my case the difference is 'crash' or 'works ok'. Another question is why should I specify direct/indirect in glXCreateContext if there is no reason to care. My longer term aim is to understand what my Radeon SE9200 can and cannot do. Mesa is so clever that it hides by software when hardware is deficient. I think that only by getting access to the the drm kernel driver can I start exploring the hardware. As John Bridgman wrote DRI might be useful too for non-GL applications, which do want contact with the X server not to clobber other windows but otherwise would like to access non-GL capabilities of the hardware or GL capabilities in a differnt way. Radeon documentation is possibly available but under non disclosure conditions which I do not want to accept. At least I found very little publicly available. In the short run I try to understand a bit better how DRI manages the relation ships between X windows, those that GLXWindows and, maybe an impossible animal, a DRM Window, which shows consideration for other X windows. Regards, Enno -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 20340] Fuzzy textures when drawing 1:1 with GL_LINEAR
http://bugs.freedesktop.org/show_bug.cgi?id=20340 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #5 from Alex Deucher ag...@yahoo.com 2009-05-13 15:58:45 PST --- committed: 038f0bf5916df5bae1145d234589e5fd528bb7fa Thanks! -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 21609] [radeon-rewrite] Use correct texture format for RGB textures
http://bugs.freedesktop.org/show_bug.cgi?id=21609 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Alex Deucher ag...@yahoo.com 2009-05-13 16:45:26 PST --- Pushed along with a fixes for r1xx and r2xx. ea6a74abbe4053b958d640425e061f0ceec92291 7cd57e35b6427068b87c2fdb6c2aadef57f53520 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 21648] [radeon-rewrite] TexImage2D, SGIS_generate_mipmap, pixels=NULL
http://bugs.freedesktop.org/show_bug.cgi?id=21648 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Alex Deucher ag...@yahoo.com 2009-05-13 16:45:56 PST --- pushed: ca792be42b238bd1c8f8a99ad72ea8558cbbfc32 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 21608] [radeon-rewrite] ctx-Stencil._Enabled stale when accessed
http://bugs.freedesktop.org/show_bug.cgi?id=21608 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from Alex Deucher ag...@yahoo.com 2009-05-13 16:46:19 PST --- committed: 34eab5dd9c837769f1259e1f900b4528586d23b2 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
