[Bug 15386] r300: Vertex program has problems with more than 7 inputs
http://bugs.freedesktop.org/show_bug.cgi?id=15386 --- Comment #7 from Markus Amsler <[EMAIL PROTECTED]> 2008-04-09 18:15:58 PST --- Created an attachment (id=15793) --> (http://bugs.freedesktop.org/attachment.cgi?id=15793) Set correct VAP_CNTL per vertex program. not sure about: - correct implemented state flush before VAP_CNTL - naming convention in r300_reg.h - delete VAP_CNTL in r300ResetHwState - whether VAP_CNTL is needed in r300EmitClearState -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: unfenced not empty what to do ?
On Wed, 09 Apr 2008 20:35:07 +0200 Thomas Hellström <[EMAIL PROTECTED]> wrote: > Jerome Glisse wrote: > > Hi Thomas, > > > > What should be done when unfenced list is not empty on module > > unload, i call drm_bo_mm_cleanup with unfenced not empty end > > i trigger : > > BUG_ON(!list_empty(&bm->unfenced)) > > > > Should the core try to flush everythings instead of BUG_ON ? > > Or should i make sure my self in the driver that everythings > > is clean ? > > > > Cheers, > > Jerome Glisse <[EMAIL PROTECTED]> > > > Jerome, > > The unfenced list should only be populated during a superioctl > (execbuffer) call. > At the end of that call, the driver should either call > a) drm_fence_buffer_objects() to fence the buffers, > b) drm_putback_buffer_objects() if command submission didn't succeed. > (see i915_handle_copyback()) > > Note that drm_fence_buffer_objects() can fail. > In that case, the driver should idle the appropriate engine and call > drm_putback_buffer_objects. (see i915_fence_or_sync()) > > If, in addition, the exebuf() call is made atomic by means of a mutex, > (replacing the hardware lock) this will guarantee that the unfenced list > is always empty after an execbuf. > > Strictly speaking, that mutex is protecting the unfenced list. > > /Thomas Thanks Thomas, this was a bug on my side one of the path in my superioctl did not have the drm_putback_buffer_objects :( I need to cleanup a bit more the code so i have one error path and one success path, this would make such bug more trivial to find. Cheers, Jerome Glisse <[EMAIL PROTECTED]> - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: unfenced not empty what to do ?
Jerome Glisse wrote: > Hi Thomas, > > What should be done when unfenced list is not empty on module > unload, i call drm_bo_mm_cleanup with unfenced not empty end > i trigger : > BUG_ON(!list_empty(&bm->unfenced)) > > Should the core try to flush everythings instead of BUG_ON ? > Or should i make sure my self in the driver that everythings > is clean ? > > Cheers, > Jerome Glisse <[EMAIL PROTECTED]> > Jerome, The unfenced list should only be populated during a superioctl (execbuffer) call. At the end of that call, the driver should either call a) drm_fence_buffer_objects() to fence the buffers, b) drm_putback_buffer_objects() if command submission didn't succeed. (see i915_handle_copyback()) Note that drm_fence_buffer_objects() can fail. In that case, the driver should idle the appropriate engine and call drm_putback_buffer_objects. (see i915_fence_or_sync()) If, in addition, the exebuf() call is made atomic by means of a mutex, (replacing the hardware lock) this will guarantee that the unfenced list is always empty after an execbuf. Strictly speaking, that mutex is protecting the unfenced list. /Thomas - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wednesday, April 09, 2008 10:39 am Jesse Barnes wrote: > > With VGA (i.e. ADPA) output ? > > > > If so, that's the problem. From what I can tell of i915 docs, they only > > support hotplug for SDVO devices only, so that's how it's coded up at > > the moment. For i945/i965 it can go the whole hog. > > Ah, maybe that's it, yeah I'm using VGA via ADPA. I don't see any IIR or > PIPEASTAT bits set when I plug in the display, so I guess we're stuck with > manually probing on these devices. Looks like i915 may support TV hotplug too, though I haven't finished the TV bits yet; I'll see about that today. However, on my 965 I get hotplug interrupts, the output is configured, and I even get uevents with the new sysfs code, yay! :) Jesse - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
unfenced not empty what to do ?
Hi Thomas, What should be done when unfenced list is not empty on module unload, i call drm_bo_mm_cleanup with unfenced not empty end i trigger : BUG_ON(!list_empty(&bm->unfenced)) Should the core try to flush everythings instead of BUG_ON ? Or should i make sure my self in the driver that everythings is clean ? Cheers, Jerome Glisse <[EMAIL PROTECTED]> - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wednesday, April 09, 2008 10:23 am Alan Hourihane wrote: > On Wed, 2008-04-09 at 09:34 -0700, Jesse Barnes wrote: > > On Wednesday, April 09, 2008 9:15 am Alan Hourihane wrote: > > > On Wed, 2008-04-09 at 08:17 -0700, Jesse Barnes wrote: > > > > On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote: > > > > > I was going to suggest that you plug it into the hotplug_stage_two > > > > > function but it looks like you have already done that. Things might > > > > > be routed differently now then since the last time I looked at the > > > > > code, are you sure that stage_two is being run? > > > > > > > > I'll have to check, I'm not sure I'm even getting interrupts... > > > > > > Jesse, > > > > > > Is this i915 or i945/i965 you are testing on ?? > > > > I've been testing on my i915 based laptop, haven't tried my other systems > > yet... > > With VGA (i.e. ADPA) output ? > > If so, that's the problem. From what I can tell of i915 docs, they only > support hotplug for SDVO devices only, so that's how it's coded up at > the moment. For i945/i965 it can go the whole hog. Ah, maybe that's it, yeah I'm using VGA via ADPA. I don't see any IIR or PIPEASTAT bits set when I plug in the display, so I guess we're stuck with manually probing on these devices. Thanks, Jesse - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wed, 2008-04-09 at 09:34 -0700, Jesse Barnes wrote: > On Wednesday, April 09, 2008 9:15 am Alan Hourihane wrote: > > On Wed, 2008-04-09 at 08:17 -0700, Jesse Barnes wrote: > > > On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote: > > > > I was going to suggest that you plug it into the hotplug_stage_two > > > > function but it looks like you have already done that. Things might be > > > > routed differently now then since the last time I looked at the code, > > > > are you sure that stage_two is being run? > > > > > > I'll have to check, I'm not sure I'm even getting interrupts... > > > > Jesse, > > > > Is this i915 or i945/i965 you are testing on ?? > > I've been testing on my i915 based laptop, haven't tried my other systems > yet... With VGA (i.e. ADPA) output ? If so, that's the problem. From what I can tell of i915 docs, they only support hotplug for SDVO devices only, so that's how it's coded up at the moment. For i945/i965 it can go the whole hog. Alan. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wednesday, April 09, 2008 9:15 am Alan Hourihane wrote: > On Wed, 2008-04-09 at 08:17 -0700, Jesse Barnes wrote: > > On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote: > > > I was going to suggest that you plug it into the hotplug_stage_two > > > function but it looks like you have already done that. Things might be > > > routed differently now then since the last time I looked at the code, > > > are you sure that stage_two is being run? > > > > I'll have to check, I'm not sure I'm even getting interrupts... > > Jesse, > > Is this i915 or i945/i965 you are testing on ?? I've been testing on my i915 based laptop, haven't tried my other systems yet... Jesse - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wed, 2008-04-09 at 08:17 -0700, Jesse Barnes wrote: > On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote: > > I was going to suggest that you plug it into the hotplug_stage_two > > function but it looks like you have already done that. Things might be > > routed differently now then since the last time I looked at the code, > > are you sure that stage_two is being run? > > I'll have to check, I'm not sure I'm even getting interrupts... Jesse, Is this i915 or i945/i965 you are testing on ?? Alan. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote: > I was going to suggest that you plug it into the hotplug_stage_two > function but it looks like you have already done that. Things might be > routed differently now then since the last time I looked at the code, > are you sure that stage_two is being run? I'll have to check, I'm not sure I'm even getting interrupts... > > Any thoughts on the interface? Anything in particular people would like > > to see? > > Looks good, can you write to dpms, that is turn a monitor on and of, > that would be slightly cool but not overly useful. On the whole I > think exporting properties are fine, but I don't think setting modes > and crtc's are to be done in sysfs. However it is entirely possible. Agreed. I view this more as a way of exporting information about the DRM configuration to userspace rather than a way to control the whole thing. I think we should stick with ioctls for the latter... Anyway thanks for checking it out. Jesse - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRM modesetting & sysfs
On Tue, Apr 8, 2008 at 10:17 PM, Jesse Barnes <[EMAIL PROTECTED]> wrote: > > I just pushed a few changes updating the DRM modesetting sysfs support, both > for debugging and eventual HAL friendliness. > > So far, the support is limited to describing outputs and generating hotplug > events. A typical "card0" directory now looks like this: > > . > |-- card0-DAC-1 > | |-- device -> ../../../../../../devices/pci:00/:00:02.0/drm/card0 > | |-- dpms > | |-- edid > | |-- modes > | |-- power > | | `-- wakeup > | |-- status > | |-- subsystem -> ../../../../../../class/drm > | `-- uevent > |-- card0-LVDS-1 > | |-- device -> ../../../../../../devices/pci:00/:00:02.0/drm/card0 > | |-- dpms > | |-- edid > | |-- modes > | |-- power > | | `-- wakeup > | |-- status > | |-- subsystem -> ../../../../../../class/drm > | `-- uevent > |-- dev > |-- device -> ../../../../../devices/pci:00/:00:02.0 > |-- dri_library_name > |-- power > | `-- wakeup > |-- subsystem -> ../../../../../class/drm > `-- uevent > > Each output is listed, prefixed with its associated card number to > disambiguate it at the top level /sys/class/drm directory (where it also has > some symlinks). Currently, only DPMS, EDID, mode list and connection status > properties are exported, but we could list more as needed. You can > use 'udevmonitor --env' to look for hotplug events; you should see several at > load time, and presumably some at connection hotplug time (though I haven't > gotten that working yet, any ideas Jakob?). > I was going to suggest that you plug it into the hotplug_stage_two function but it looks like you have already done that. Things might be routed differently now then since the last time I looked at the code, are you sure that stage_two is being run? > Any thoughts on the interface? Anything in particular people would like to > see? > Looks good, can you write to dpms, that is turn a monitor on and of, that would be slightly cool but not overly useful. On the whole I think exporting properties are fine, but I don't think setting modes and crtc's are to be done in sysfs. However it is entirely possible. > Thanks, > Jesse Cheers Jakob. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 7770] PCI domain mismatch between X server and kernel, leaving clients unable to use direct rendering
http://bugs.freedesktop.org/show_bug.cgi?id=7770 --- Comment #36 from Marcin Kurek <[EMAIL PROTECTED]> 2008-04-09 00:39:53 PST --- Created an attachment (id=15774) --> (http://bugs.freedesktop.org/attachment.cgi?id=15774) quick drm domain patch -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 7770] PCI domain mismatch between X server and kernel, leaving clients unable to use direct rendering
http://bugs.freedesktop.org/show_bug.cgi?id=7770 --- Comment #35 from Marcin Kurek <[EMAIL PROTECTED]> 2008-04-09 00:39:24 PST --- Sure. It was just a quick hack to see is this would fix the problem here. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8891] Refreshing parts of the screen incorrect/not working
http://bugs.freedesktop.org/show_bug.cgi?id=8891 Michel Dänzer <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #5 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-09 00:32:37 PST --- Assuming this is related to comment #4. Please don't reopen without at least attaching full xorg.conf and Xorg.0.log. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 7770] PCI domain mismatch between X server and kernel, leaving clients unable to use direct rendering
http://bugs.freedesktop.org/show_bug.cgi?id=7770 --- Comment #34 from Michel Dänzer <[EMAIL PROTECTED]> 2008-04-09 00:03:48 PST --- (In reply to comment #33) > It seems you have right as there is no crash when I replace the hardcoded > domain from 0 to pci_domain_nr() in drmP.h. Can you provide a patch for that? Unfortunately, this change will probably break older X servers that hardcoded the domain to 0, so a full solution may require some DRM interface versioning magic. > Error: couldn't find RGB GLX visual That's a different issue which should be fixed now in Mesa Git. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
