date:20100209

[Bug 15120] laptop hangs up on s2disk - Lenovo thinkpad T61

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15120





--- Comment #18 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
09:48:57 ---
So, did anybody from nouveau team notice this report?

-- 
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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15151] Black screen after loading nouveau module

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15151





--- Comment #12 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
09:54:38 ---
This patch failed when I tried to apply it to 2.6.33-rc7 (I haven't got time
to test it early)

On Tue, Feb 2, 2010 at 11:21 PM, bugzilla-dae...@bugzilla.kernel.orgwrote:

 http://bugzilla.kernel.org/show_bug.cgi?id=15151





 --- Comment #11 from Marcin Slusarz marcin.slus...@gmail.com  2010-02-02
 21:21:35 ---
 Created an attachment (id=24883)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
  -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
 efifb fix

 --
 Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
 --- You are receiving this mail because: ---
 You reported the bug.


-- 
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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: Removal of mach64

2010-02-09 Thread Catalin Patulea

Hmm, I was able to get the driver working, but I have some more
questions; let me first give you some background.

My box is a Dell PowerEdge 1600SC server with an integrated ATI Rage XL:
$ sudo lspci -vs 0e
00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
Subsystem: Dell Device 0135
Flags: bus master, VGA palette snoop, stepping, medium devsel,
latency 32
Memory at fd00 (32-bit, non-prefetchable) [size=16M]
I/O ports at e800 [size=256]
Memory at fe121000 (32-bit, non-prefetchable) [size=4K]
[virtual] Expansion ROM at c000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 2

I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
Perhaps that's just the size of the window but only 8M is physically
present.

I have compiled the kernel mach64 DRM driver from Archlinux, posted by
Alexander Lam (many thanks for that), and it seems I can enable DRI
with 1024x768x16, but I get the following (EE):
(II) MACH64(0): [DRI] installation complete
(II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
(II) MACH64(0): [drm] Mapped 128 DMA buffers at 0xb66db000
(EE) MACH64(0): [drm] Couldn't find IRQ for bus id 0:14:0
(II) MACH64(0): [drm] Falling back to irq-free operation
(II) MACH64(0): Direct rendering enabled

Given the (II) following it, this seems to be more of a warning.
Indeed, the device doesn't have an IRQ in lspci or /proc/interrupts.
Is there anything I can do about this? Any particular performance
issues I should see due to lack of an IRQ?

The other question is regarding running DRI with a higher resolution,
1280x1024x16 (since that's my LCD's native resolution ;-) ). I get the
following:
(II) MACH64(0): [drm] Will request asynchronous DMA mode
(==) MACH64(0): [drm] Using 2 MB for DMA buffers
(II) MACH64(0): [pci] ring handle = 0x36224000
(II) MACH64(0): [pci] Ring mapped at 0xb699d000
(II) MACH64(0): [drm] register handle = 0xfe121000
(II) MACH64(0): [dri] Visual configs initialized
(II) MACH64(0): [dri] Block 0 base at 0xfe121400
(WW) MACH64(0): Not enough memory for local textures, disabling DRI
(II) MACH64(0): [drm] removed 1 reserved context for kernel
(II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xf8035000 at 0xb69a1000
(II) MACH64(0): [drm] Closed DRM master.
(II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
[...]
(II) MACH64(0): Direct rendering disabled

Is there any way to get DRI with this higher resolution? Perhaps by
reducing the (2 MB) DMA allocation?

It seems to me like 1280x1024x16 / 8 = 2.5 MBytes should fit pretty
easily.. why do I seem to need a lot more memory for this resolution?

And lastly, with 1024x768x16 and DRI enabled, I still see (relatively)
high CPU usage by Xorg when dragging windows around (70% on a 2 GHz
P4).. any hints on reducing that?

Thanks,

Catalin

2010/2/7 Catalin Patulea c...@vv.carleton.ca:
 2010/2/7 Kristian Høgsberg k...@bitplanet.net:
 They live in the kernel.
 I can't seem to find them there.. perhaps I'm looking in the wrong place:
 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/gpu/drm


--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [PATCH] i915 / PM: Fix crash while aborting hibernation (Re: [linux-pm] [regression] drm/i915: implement new pm ops disables irq on aborted s2disk)

2010-02-09 Thread Alan Jenkins

Rafael J. Wysocki wrote:
 On Thursday 04 February 2010, Zhenyu Wang wrote:
   
 On 2010.02.03 23:44:41 +0100, Rafael J. Wysocki wrote:
 
 On Wednesday 03 February 2010, Alan Jenkins wrote:
   
 Hi

 I found this regression on my EeePC 701 with modesetting enabled.  When 
 I hibernate using s2disk, I can abort the hibernation by pressing the 
 backspace key.  Doing so breaks X on 2.6.32-rc6 (but not 2.6.32).
 
 Yeah.

 To be honest, I knew that's going to happen, but didn't have the time to 
 take
 care of it.

 The problem is that i915 does literally _nothing_ in its .thaw() callback,
 although it should at least reverse whatever .freeze() did to the hardware
 (and memory allocations and so on), so that the adapter is functional
 after creating the image.

 Fixing this requires some thought, though, because at the moment .freeze()
 thinks it's .suspend(), which is not the case as this report clearly shows.
 So, in fact i915_pci_suspend() has to be split into the .freeze() part and
 the poweroff part cleanly and that's not  so simple (at least to me).

   
 Right, I think that'll be more clean, stuff in i915_save/restore_state() need
 to be splited too, especially isolate stuff for mode setting and other device
 state, as what my original purpose for this is to remove extra mode setting 
 cycle in old behavior so not waste time for hibernate.
 

 We can't really do that, because we'll need to restore the saved state at the
 resume-from-hibernation stage.

 The appended patch fixes the issue for me, although it's been only tested
 a little.  It sort of defeats the purpose of commit
 cbda12d77ea590082edb6d30bd342a67ebc459e0, but I don't see any less invasive
 way to fix this except maybe for reverting that commit entirely.

 Note that the drm_irq_[un]install() thing may be unnecessary, but I wasn't 
 sure
 about that and surely wouldn't suggest doing that for 2.6.33.  Also it looks 
 like
 some things from the freeze and thaw parts may be moved to the low-level
 suspend and resume parts, respectively, but that would require some
 i915_gem_* surgery I was too scared to do.

 Alan, please test, i915 guys, please review.

 Rafael
   

The patch works very nicely on my eeepc.

Thanks
(and thanks again for all your hard work this cycle, and specifically 
for pointing me to the s2disk hang-fix)

Alan

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15120] laptop hangs up on s2disk - Lenovo thinkpad T61

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15120





--- Comment #19 from Rafael J. Wysocki r...@sisk.pl  2010-02-09 12:42:00 ---
Switching to e-mail.

On Tuesday 09 February 2010, bugzilla-dae...@bugzilla.kernel.org wrote:
 http://bugzilla.kernel.org/show_bug.cgi?id=15120
 
 --- Comment #18 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
 09:48:57 ---
 So, did anybody from nouveau team notice this report?

Apparently not, so let's CC them.

-- 
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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Bug 15120] laptop hangs up on s2disk - Lenovo thinkpad T61

2010-02-09 Thread Rafael J. Wysocki

Switching to e-mail.

On Tuesday 09 February 2010, bugzilla-dae...@bugzilla.kernel.org wrote:
 http://bugzilla.kernel.org/show_bug.cgi?id=15120
 
 --- Comment #18 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
 09:48:57 ---
 So, did anybody from nouveau team notice this report?

Apparently not, so let's CC them.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

vmwgfx + VMWare 7.0 - libdrm modetest.c

2010-02-09 Thread Peter Hanzel

Hello.

I have a question about libdrm/libkms and test/modetest/modetest.c.
I am now working with vmwgfx + VMWare 7.0, where vmwgfx had correctly 
initialized framebuffer and also now using fbcon.
Now I want to test it woth modetest.c
This program is only for intel so i recoded it to use libkms functions.

I had to add:

struct kms_bo
{
 struct kms_driver *kms;
 void *ptr;
 size_t size;
 size_t offset;
 size_t pitch;
 unsigned handle;
};

to modetest.c to compile it.

Now the test can set mode. I have tested 800x600 and also 1024x768.
But my problem is that screen is always black. If you take a look into 
modetest.c it is making that nice one tilled colour screen.

The problem lines are in:

libkms/vmwgfx.c

static int
vmwgfx_bo_create(struct kms_driver *kms,
   const unsigned width, const unsigned height,
   const enum kms_bo_type type, const unsigned *attr,
   struct kms_bo **out)
{

do {
   ret = drmCommandWriteRead(bo-base.kms-fd,
DRM_VMW_ALLOC_DMABUF,
arg, sizeof(arg));
  } while (ret == -ERESTART);

  if (ret)
   goto err_free;

  bo-base.handle = rep-handle;
  bo-map_handle = rep-map_handle;
  bo-base.handle = rep-cur_gmr_id;
  bo-base.offset = rep-cur_gmr_offset;

As you can see, there is:
  bo-base.handle = rep-handle;
  bo-base.handle = rep-cur_gmr_id;

So it is overwiting the same base.handle.

This handle I am using in modetest.c - drmModeAddFB().   maybe here is 
error,
bo-base.handle is not the correct one for use in drmModeAddFB( 
bo-handle)

So my question is:
 1) The need of define for strcut kms_bo (is is located in 
libkms/internal.h)
 2) Why the screen is still black?

Thanks.




--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [PATCH 1/2] drm: introduce drm_gem_object_[handle_]unreference_unlocked

2010-02-09 Thread Daniel Vetter

On Tue, Feb 09, 2010 at 06:49:11AM +0100, Luca Barbieri wrote:
 This patch introduces the drm_gem_object_unreference_unlocked
 and drm_gem_object_handle_unreference_unlocked functions that
 do not require holding struct_mutex.
 
 drm_gem_object_unreference_unlocked calls the new
 -gem_free_object_unlocked entry point if available, and
 otherwise just takes struct_mutex and just calls -gem_free_object

Why not add a BUG_ON(!mutex_is_locked(dev-struct_mutex)) to
drm_gem_object_unreference to catch wrong api by occasional drm hackers
like me?

-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [PATCH 2/2] Use drm_gem_object_[handle_]unreference_unlocked where possible

2010-02-09 Thread Daniel Vetter

On Tue, Feb 09, 2010 at 06:49:12AM +0100, Luca Barbieri wrote:
 Mostly obvious simplifications.
 
 The i915 pread/pwrite ioctls, intel_overlay_put_image and
 nouveau_gem_new were incorrectly using the locked versions
 without locking: this is also fixed in this patch.

Just one nitpick on the intel_overlay.c part ..

 diff --git a/drivers/gpu/drm/i915/intel_overlay.c 
 b/drivers/gpu/drm/i915/intel_overlay.c
 index 2639591..1b50d61 100644
 --- a/drivers/gpu/drm/i915/intel_overlay.c
 +++ b/drivers/gpu/drm/i915/intel_overlay.c
 @@ -1179,7 +1179,7 @@ int intel_overlay_put_image(struct drm_device *dev, 
 void *data,
  out_unlock:
   mutex_unlock(dev-struct_mutex);
   mutex_unlock(dev-mode_config.mutex);
 - drm_gem_object_unreference(new_bo);
 + drm_gem_object_unreference_unlocked(new_bo);
   kfree(params);

Just move the drm_gem_object_unreference before the mutex_unlock calls,
make more sense that way, IMHO.

-Daniel
-- 
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26087] Stalls with RV635 with KMS

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26087





--- Comment #13 from Ming-Wei Shih xming...@gmail.com  2010-02-09 05:59:54 
PST ---
Created an attachment (id=33193)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=33193)
.config

I am having stall issues too for some time, it's getting worse (more frequent
stalls and last longer. When running glx-gears (with kde4 composite on) and
move the mouse around a bit I get this according to latencytop

radeon_ring_lock radeon_ib_schedule radeon_cs_ioct195.2 msec  0.9 %

Attached is my .config.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26087] Stalls with RV635 with KMS

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26087





--- Comment #14 from Ming-Wei Shih xming...@gmail.com  2010-02-09 06:02:59 
PST ---
more about my setup,

I am using kms with irq.

kernel: drm-radeon-testing
mesa: git
ddx: git
libdrm: git

00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge
(rev a2)
01:00.0 VGA compatible controller: ATI Technologies Inc RV670 AGP [Radeon HD
3850]

CPU: model name  : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: vmwgfx + VMWare 7.0 - libdrm modetest.c

2010-02-09 Thread Jakob Bornecrantz

On 9 feb 2010, at 13.05, Peter Hanzel wrote:
 Hello.

 I have a question about libdrm/libkms and test/modetest/modetest.c.
 I am now working with vmwgfx + VMWare 7.0, where vmwgfx had correctly
 initialized framebuffer and also now using fbcon.
 Now I want to test it woth modetest.c
 This program is only for intel so i recoded it to use libkms  
 functions.

 I had to add:

 struct kms_bo
 {
 struct kms_driver *kms;
 void *ptr;
 size_t size;
 size_t offset;
 size_t pitch;
 unsigned handle;
 };

 to modetest.c to compile it.

 Now the test can set mode. I have tested 800x600 and also 1024x768.
 But my problem is that screen is always black. If you take a look into
 modetest.c it is making that nice one tilled colour screen.

 The problem lines are in:

 libkms/vmwgfx.c

 static int
 vmwgfx_bo_create(struct kms_driver *kms,
   const unsigned width, const unsigned height,
   const enum kms_bo_type type, const unsigned *attr,
   struct kms_bo **out)
 {
 
 do {
   ret = drmCommandWriteRead(bo-base.kms-fd,
DRM_VMW_ALLOC_DMABUF,
arg, sizeof(arg));
  } while (ret == -ERESTART);

  if (ret)
   goto err_free;

  bo-base.handle = rep-handle;
  bo-map_handle = rep-map_handle;
  bo-base.handle = rep-cur_gmr_id;
  bo-base.offset = rep-cur_gmr_offset;

 As you can see, there is:
  bo-base.handle = rep-handle;
  bo-base.handle = rep-cur_gmr_id;

 So it is overwiting the same base.handle.

 This handle I am using in modetest.c - drmModeAddFB().   maybe  
 here is
 error,
bo-base.handle is not the correct one for use in drmModeAddFB(
 bo-handle)

 So my question is:
 1) The need of define for strcut kms_bo (is is located in
 libkms/internal.h)

struct kms_bo is a internal resource to the libkms interface, it  
should be opaque to the user but to the internal code. All the buffer  
exposes pretty much the same set of information to the user but might  
need extra information attached. Defining a base kms_bo object that  
backends can use as a baseclass allows code to be shared.

 2) Why the screen is still black?

You need to use the drmModeDirtyFB ioctl/function to tell the Kernel  
to update the screen. Just call it like so drmModeDirtyFB(fd, fb,  
NULL, 0); and it should update the whole screen.

Cheers Jakob.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: Removal of mach64

2010-02-09 Thread Alexander Lam

2010/2/9 Catalin Patulea c...@vv.carleton.ca:
 Hmm, I was able to get the driver working, but I have some more
 questions; let me first give you some background.

 My box is a Dell PowerEdge 1600SC server with an integrated ATI Rage XL:
 $ sudo lspci -vs 0e
 00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
        Subsystem: Dell Device 0135
        Flags: bus master, VGA palette snoop, stepping, medium devsel,
 latency 32
        Memory at fd00 (32-bit, non-prefetchable) [size=16M]
        I/O ports at e800 [size=256]
        Memory at fe121000 (32-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at c000 [disabled] [size=128K]
        Capabilities: [5c] Power Management version 2

 I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
 Perhaps that's just the size of the window but only 8M is physically
 present.

 I have compiled the kernel mach64 DRM driver from Archlinux, posted by
 Alexander Lam (many thanks for that), and it seems I can enable DRI
 with 1024x768x16, but I get the following (EE):
 (II) MACH64(0): [DRI] installation complete
 (II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
 (II) MACH64(0): [drm] Mapped 128 DMA buffers at 0xb66db000
 (EE) MACH64(0): [drm] Couldn't find IRQ for bus id 0:14:0
 (II) MACH64(0): [drm] Falling back to irq-free operation
 (II) MACH64(0): Direct rendering enabled

 Given the (II) following it, this seems to be more of a warning.
 Indeed, the device doesn't have an IRQ in lspci or /proc/interrupts.
 Is there anything I can do about this? Any particular performance
 issues I should see due to lack of an IRQ?

I don't know if there are performance issues without an IRQ, but for
my computer's add-on AGP card, there is a jumper labeled INTVGA that
enables/disables the IRQ. Perhaps check your system's manual?



-- 
Alexander Lam

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: vmwgfx + VMWare 7.0 - libdrm modetest.c

2010-02-09 Thread Kristian Høgsberg

On Tue, Feb 9, 2010 at 8:05 AM, Peter Hanzel hanzelpe...@gmail.com wrote:
 Hello.

 I have a question about libdrm/libkms and test/modetest/modetest.c.
 I am now working with vmwgfx + VMWare 7.0, where vmwgfx had correctly
 initialized framebuffer and also now using fbcon.
 Now I want to test it woth modetest.c
 This program is only for intel so i recoded it to use libkms functions.

Could you send the changes to make modetest.c use libkms as a patch?
It's a good idea.

cheers,
Kristian

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Bugme-new] [Bug 15248] New: KMS broken on Intel 855GM broken with 2.6.32/33

2010-02-09 Thread Rafael J. Wysocki

On Tuesday 09 February 2010, Andrew Morton wrote:
 On Sun, 7 Feb 2010 09:59:06 GMT
 bugzilla-dae...@bugzilla.kernel.org wrote:
 
  http://bugzilla.kernel.org/show_bug.cgi?id=15248
 
 DRI/KMS regression #1,987,776

Added, CCing dri-devel and the i915 maintainers.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26471] Missing background graphics/texture in frogatto with R600 (RV670)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26471





--- Comment #8 from Nils Kneuper crazy-ivano...@gmx.net  2010-02-09 06:56:49 
PST ---
To make sure to get a version that does compile and link, please use this
checkout link:
svn checkout -r 1712 http://frogatto.googlecode.com/svn/trunk/
frogatto-read-only

You still have to update the Makefile, this sed command does the job:
sed -i s/ -lprofiler//g Makefile


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: Removal of mach64

2010-02-09 Thread Alex Deucher

2010/2/9 Catalin Patulea c...@vv.carleton.ca:
 Hmm, I was able to get the driver working, but I have some more
 questions; let me first give you some background.

 My box is a Dell PowerEdge 1600SC server with an integrated ATI Rage XL:
 $ sudo lspci -vs 0e
 00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
        Subsystem: Dell Device 0135
        Flags: bus master, VGA palette snoop, stepping, medium devsel,
 latency 32
        Memory at fd00 (32-bit, non-prefetchable) [size=16M]
        I/O ports at e800 [size=256]
        Memory at fe121000 (32-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at c000 [disabled] [size=128K]
        Capabilities: [5c] Power Management version 2

 I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
 Perhaps that's just the size of the window but only 8M is physically
 present.

That's just the size of the aperture.  The driver will detect the
proper amount of vram installed.


 I have compiled the kernel mach64 DRM driver from Archlinux, posted by
 Alexander Lam (many thanks for that), and it seems I can enable DRI

If one of you can port it to the latest kernel bits, we could get it
upstream finally.

 with 1024x768x16, but I get the following (EE):
 (II) MACH64(0): [DRI] installation complete
 (II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
 (II) MACH64(0): [drm] Mapped 128 DMA buffers at 0xb66db000
 (EE) MACH64(0): [drm] Couldn't find IRQ for bus id 0:14:0
 (II) MACH64(0): [drm] Falling back to irq-free operation
 (II) MACH64(0): Direct rendering enabled

 Given the (II) following it, this seems to be more of a warning.
 Indeed, the device doesn't have an IRQ in lspci or /proc/interrupts.
 Is there anything I can do about this? Any particular performance
 issues I should see due to lack of an IRQ?


You might check if your bios has an option to enable an irq for vga
devices.  You'll need an irq for vblank support, but beyond that I
don't recall what else the mach64 could use irqs for.

 The other question is regarding running DRI with a higher resolution,
 1280x1024x16 (since that's my LCD's native resolution ;-) ). I get the
 following:
 (II) MACH64(0): [drm] Will request asynchronous DMA mode
 (==) MACH64(0): [drm] Using 2 MB for DMA buffers
 (II) MACH64(0): [pci] ring handle = 0x36224000
 (II) MACH64(0): [pci] Ring mapped at 0xb699d000
 (II) MACH64(0): [drm] register handle = 0xfe121000
 (II) MACH64(0): [dri] Visual configs initialized
 (II) MACH64(0): [dri] Block 0 base at 0xfe121400
 (WW) MACH64(0): Not enough memory for local textures, disabling DRI
 (II) MACH64(0): [drm] removed 1 reserved context for kernel
 (II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xf8035000 at 0xb69a1000
 (II) MACH64(0): [drm] Closed DRM master.
 (II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        Indirect CPU to Screen color expansion
        Solid Lines
 [...]
 (II) MACH64(0): Direct rendering disabled

 Is there any way to get DRI with this higher resolution? Perhaps by
 reducing the (2 MB) DMA allocation?

 It seems to me like 1280x1024x16 / 8 = 2.5 MBytes should fit pretty
 easily.. why do I seem to need a lot more memory for this resolution?


You need 2.5 MBytes for the front buffer, back buffer, and Z buffer
which will eat 7.5 MBytes.  The remaining 0.5 MBytes is all you have
left for hw cursors, X pixmaps, and textures.  To fix it properly you
really need a unified memory manager so you don't have the huge static
allocations.

 And lastly, with 1024x768x16 and DRI enabled, I still see (relatively)
 high CPU usage by Xorg when dragging windows around (70% on a 2 GHz
 P4).. any hints on reducing that?

DRI has nothing to do with 2D stuff.  It only accelerates 3D (OpenGL).
 You might try switching to EXA:
Option AccelMethod EXA
Or lowering your resolution to free up more offscreen memory for 2D.

Alex


 Thanks,

 Catalin

 2010/2/7 Catalin Patulea c...@vv.carleton.ca:
 2010/2/7 Kristian Høgsberg k...@bitplanet.net:
 They live in the kernel.
 I can't seem to find them there.. perhaps I'm looking in the wrong place:
 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/gpu/drm


 --
 The Planet: dedicated and managed hosting, cloud storage, colocation
 Stay online with enterprise data centers and the best network in the business
 Choose flexible plans and management services without long-term contracts
 Personal 24x7 support from experience hosting pros just a phone call away.
 http://p.sf.net/sfu/theplanet-com
 --
 ___
 Dri-devel mailing list
 Dri-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dri-devel


--
The Planet: dedicated

Re: Removal of mach64

2010-02-09 Thread Ville Syrjälä

On Tue, Feb 09, 2010 at 03:40:34AM -0500, Catalin Patulea wrote:
 Hmm, I was able to get the driver working, but I have some more
 questions; let me first give you some background.
 
 My box is a Dell PowerEdge 1600SC server with an integrated ATI Rage XL:
 $ sudo lspci -vs 0e
 00:0e.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
 Subsystem: Dell Device 0135
 Flags: bus master, VGA palette snoop, stepping, medium devsel,
 latency 32
 Memory at fd00 (32-bit, non-prefetchable) [size=16M]
 I/O ports at e800 [size=256]
 Memory at fe121000 (32-bit, non-prefetchable) [size=4K]
 [virtual] Expansion ROM at c000 [disabled] [size=128K]
 Capabilities: [5c] Power Management version 2
 
 I'm fairly sure it has 8M of video RAM -- not sure why that says 16M.
 Perhaps that's just the size of the window but only 8M is physically
 present.

The 16MB is split into two apertures. They both point to the same memory
area but the byte swapping for each can be controlled independently.
You can actually have 16MB of memory on a Rage Pro but the CPU can't
directly access all of it.

 I have compiled the kernel mach64 DRM driver from Archlinux, posted by
 Alexander Lam (many thanks for that), and it seems I can enable DRI
 with 1024x768x16, but I get the following (EE):
 (II) MACH64(0): [DRI] installation complete
 (II) MACH64(0): [drm] Added 128 16384 byte DMA buffers
 (II) MACH64(0): [drm] Mapped 128 DMA buffers at 0xb66db000
 (EE) MACH64(0): [drm] Couldn't find IRQ for bus id 0:14:0
 (II) MACH64(0): [drm] Falling back to irq-free operation
 (II) MACH64(0): Direct rendering enabled
 
 Given the (II) following it, this seems to be more of a warning.
 Indeed, the device doesn't have an IRQ in lspci or /proc/interrupts.
 Is there anything I can do about this? Any particular performance
 issues I should see due to lack of an IRQ?

There may be a jumper on the card to enable/disable the IRQ. At least
I'm pretty sure older mach64 cards had them. I don't know if integrated
mach64s generally had such jumpers or not. Perhaps the BIOS has an
option whether to assign an IRQ to the graphics card.

 The other question is regarding running DRI with a higher resolution,
 1280x1024x16 (since that's my LCD's native resolution ;-) ). I get the
 following:
 (II) MACH64(0): [drm] Will request asynchronous DMA mode
 (==) MACH64(0): [drm] Using 2 MB for DMA buffers
 (II) MACH64(0): [pci] ring handle = 0x36224000
 (II) MACH64(0): [pci] Ring mapped at 0xb699d000
 (II) MACH64(0): [drm] register handle = 0xfe121000
 (II) MACH64(0): [dri] Visual configs initialized
 (II) MACH64(0): [dri] Block 0 base at 0xfe121400
 (WW) MACH64(0): Not enough memory for local textures, disabling DRI
 (II) MACH64(0): [drm] removed 1 reserved context for kernel
 (II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xf8035000 at 0xb69a1000
 (II) MACH64(0): [drm] Closed DRM master.
 (II) MACH64(0): Using XFree86 Acceleration Architecture (XAA)
 Screen to screen bit blits
 Solid filled rectangles
 8x8 mono pattern filled rectangles
 Indirect CPU to Screen color expansion
 Solid Lines
 [...]
 (II) MACH64(0): Direct rendering disabled
 
 Is there any way to get DRI with this higher resolution? Perhaps by
 reducing the (2 MB) DMA allocation?

That 2MB is in system RAM so it would not help.

 It seems to me like 1280x1024x16 / 8 = 2.5 MBytes should fit pretty
 easily.. why do I seem to need a lot more memory for this resolution?

Back buffer and depth buffer make that 7.5 MB.

You seem to have a PCI mach64. If you had an AGP version it could use
AGP memory for texturing, or at least the hardware would allow it, I
don't know about the driver though.

-- 
Ville Syrjälä
syrj...@sci.fi
http://www.sci.fi/~syrjala/

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: Problem with drm-radeon-testing commit - drm/ttm: Avoid conflicting reserve_memtype during ttm_tt_set_page_caching.

2010-02-09 Thread Andy Furniss

Andy Furniss wrote:

 db78e27de7e29a6db6be7caf607cf803d84094aa is first bad commit

I have confirmed by running both todays and yesterdays heads with and 
without that commit reverted that it is the one causing the problem.

Another test I tried was with agpmode=-1. This does avoid the problem, 
but unfortunately it is useless as a workaround for me as game perf 
other than openarena has always been poor using pcie gart.

eg. Nexuiz timedemo demos/demo1

KMS agpmode=4

result 1910 frames 70.483 seconds 27.0987330 fps, one-second fps 
min/avg/max: 19 28 47

KMS agpmode=-1 (or UMS with either gart)

result 1910 frames 254.266 seconds 7.5118183 fps, one-second fps 
min/avg/max: 4 10 36

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26471] Missing background graphics/texture in frogatto with R600 (RV670)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26471





--- Comment #9 from Michael de Lang kingo...@gmail.com  2010-02-09 08:52:36 
PST ---
I can confirm this on a Radeon 4550(RV710).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15151] Black screen after loading nouveau module

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15151





--- Comment #13 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
17:34:09 ---
Yeah sorry for last post, patch applied correctly, I just mixed up patch
option -p0 instead of -p1 when tried to apply it

On Tue, Feb 9, 2010 at 11:54 AM, bugzilla-dae...@bugzilla.kernel.orgwrote:

 http://bugzilla.kernel.org/show_bug.cgi?id=15151





 --- Comment #12 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09
 09:54:38 ---
 This patch failed when I tried to apply it to 2.6.33-rc7 (I haven't got
 time
 to test it early)

 On Tue, Feb 2, 2010 at 11:21 PM, bugzilla-dae...@bugzilla.kernel.org
 wrote:

  http://bugzilla.kernel.org/show_bug.cgi?id=15151
 
 
 
 
 
  --- Comment #11 from Marcin Slusarz marcin.slus...@gmail.com
  2010-02-02
  21:21:35 ---
  Created an attachment (id=24883)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
  -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
   -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
  efifb fix
 
  --
  Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
  --- You are receiving this mail because: ---
  You reported the bug.
 

 --
 Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
 --- You are receiving this mail because: ---
 You reported the bug.


-- 
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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15151] Black screen after loading nouveau module

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15151





--- Comment #14 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09 
17:46:31 ---
I recompiled the kernel with this patch and it works, thx a lot :)

On Tue, Feb 9, 2010 at 7:34 PM, bugzilla-dae...@bugzilla.kernel.org wrote:

 http://bugzilla.kernel.org/show_bug.cgi?id=15151





 --- Comment #13 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09
 17:34:09 ---
 Yeah sorry for last post, patch applied correctly, I just mixed up patch
 option -p0 instead of -p1 when tried to apply it

 On Tue, Feb 9, 2010 at 11:54 AM, bugzilla-dae...@bugzilla.kernel.org
 wrote:

  http://bugzilla.kernel.org/show_bug.cgi?id=15151
 
 
 
 
 
  --- Comment #12 from Alex Zhavnerchik alex.vi...@gmail.com  2010-02-09
  09:54:38 ---
  This patch failed when I tried to apply it to 2.6.33-rc7 (I haven't got
  time
  to test it early)
 
  On Tue, Feb 2, 2010 at 11:21 PM, bugzilla-dae...@bugzilla.kernel.org
  wrote:
 
   http://bugzilla.kernel.org/show_bug.cgi?id=15151
  
  
  
  
  
   --- Comment #11 from Marcin Slusarz marcin.slus...@gmail.com
   2010-02-02
   21:21:35 ---
   Created an attachment (id=24883)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
  -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
   -- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
-- (http://bugzilla.kernel.org/attachment.cgi?id=24883)
   efifb fix
  
   --
   Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
   --- You are receiving this mail because: ---
   You reported the bug.
  
 
  --
  Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
  --- You are receiving this mail because: ---
  You reported the bug.
 

 --
 Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
 --- You are receiving this mail because: ---
 You reported the bug.


-- 
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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 23648] KMS/DRI2 Radeon Mobility 7500 Googleearth crash

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=23648





--- Comment #3 from Eduardo Durany edura...@gmail.com  2010-02-09 10:51:39 
PST ---
Everything is ok now. Running Ubuntu Karmic with xorg-edgers ppa.

kernel  2.6.33-rc7
libdrm  2.4.17+git20100209.fdcde592-0ubuntu0sarvatt~karmic
mesa7.8.0~git20100206.fd2378e4-0ubuntu0sarvatt~karmic
xorg-server
2:1.6.5+git20091107+server-1.6-branch.2dbcb06a-0ubuntu0sarvatt~karmic

3D is working and my system is not crashing (with kernel 2.6.32 my system
freezes randomly)

This bug can be closed.

A lot of 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 Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 23648] KMS/DRI2 Radeon Mobility 7500 Googleearth crash

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=23648


Alex Deucher ag...@yahoo.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[PATCH] drm/vmwgfx: Fix a circular locking dependency bug.

2010-02-09 Thread Jakob Bornecrantz

From: Thomas Hellstrom thellst...@vmware.com

Signed-off-by: Thomas Hellstrom thellst...@vmware.com
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |3 ++-
 drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c |   17 +
 drivers/gpu/drm/vmwgfx/vmwgfx_irq.c  |   13 +++--
 3 files changed, 14 insertions(+), 19 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
index 0eaf682..9c89868 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
@@ -113,6 +113,7 @@ struct vmw_fifo_state {
unsigned long static_buffer_size;
bool using_bounce_buffer;
uint32_t capabilities;
+   struct mutex fifo_mutex;
struct rw_semaphore rwsem;
 };
 
@@ -213,7 +214,7 @@ struct vmw_private {
 * Fencing and IRQs.
 */
 
-   uint32_t fence_seq;
+   atomic_t fence_seq;
wait_queue_head_t fence_queue;
wait_queue_head_t fifo_queue;
atomic_t fence_queue_waiters;
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c
index 4157547..39d43a0 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c
@@ -74,6 +74,7 @@ int vmw_fifo_init(struct vmw_private *dev_priv, struct 
vmw_fifo_state *fifo)
fifo-reserved_size = 0;
fifo-using_bounce_buffer = false;
 
+   mutex_init(fifo-fifo_mutex);
init_rwsem(fifo-rwsem);
 
/*
@@ -117,7 +118,7 @@ int vmw_fifo_init(struct vmw_private *dev_priv, struct 
vmw_fifo_state *fifo)
 (unsigned int) min,
 (unsigned int) fifo-capabilities);
 
-   dev_priv-fence_seq = dev_priv-last_read_sequence;
+   atomic_set(dev_priv-fence_seq, dev_priv-last_read_sequence);
iowrite32(dev_priv-last_read_sequence, fifo_mem + SVGA_FIFO_FENCE);
 
return vmw_fifo_send_fence(dev_priv, dummy);
@@ -283,7 +284,7 @@ void *vmw_fifo_reserve(struct vmw_private *dev_priv, 
uint32_t bytes)
uint32_t reserveable = fifo_state-capabilities  SVGA_FIFO_CAP_RESERVE;
int ret;
 
-   down_write(fifo_state-rwsem);
+   mutex_lock(fifo_state-fifo_mutex);
max = ioread32(fifo_mem + SVGA_FIFO_MAX);
min = ioread32(fifo_mem + SVGA_FIFO_MIN);
next_cmd = ioread32(fifo_mem + SVGA_FIFO_NEXT_CMD);
@@ -351,7 +352,7 @@ void *vmw_fifo_reserve(struct vmw_private *dev_priv, 
uint32_t bytes)
}
 out_err:
fifo_state-reserved_size = 0;
-   up_write(fifo_state-rwsem);
+   mutex_unlock(fifo_state-fifo_mutex);
return NULL;
 }
 
@@ -426,6 +427,7 @@ void vmw_fifo_commit(struct vmw_private *dev_priv, uint32_t 
bytes)
 
}
 
+   down_write(fifo_state-rwsem);
if (fifo_state-using_bounce_buffer || reserveable) {
next_cmd += bytes;
if (next_cmd = max)
@@ -437,8 +439,9 @@ void vmw_fifo_commit(struct vmw_private *dev_priv, uint32_t 
bytes)
if (reserveable)
iowrite32(0, fifo_mem + SVGA_FIFO_RESERVED);
mb();
-   vmw_fifo_ping_host(dev_priv, SVGA_SYNC_GENERIC);
up_write(fifo_state-rwsem);
+   vmw_fifo_ping_host(dev_priv, SVGA_SYNC_GENERIC);
+   mutex_unlock(fifo_state-fifo_mutex);
 }
 
 int vmw_fifo_send_fence(struct vmw_private *dev_priv, uint32_t *sequence)
@@ -451,9 +454,7 @@ int vmw_fifo_send_fence(struct vmw_private *dev_priv, 
uint32_t *sequence)
 
fm = vmw_fifo_reserve(dev_priv, bytes);
if (unlikely(fm == NULL)) {
-   down_write(fifo_state-rwsem);
-   *sequence = dev_priv-fence_seq;
-   up_write(fifo_state-rwsem);
+   *sequence = atomic_read(dev_priv-fence_seq);
ret = -ENOMEM;
(void)vmw_fallback_wait(dev_priv, false, true, *sequence,
false, 3*HZ);
@@ -461,7 +462,7 @@ int vmw_fifo_send_fence(struct vmw_private *dev_priv, 
uint32_t *sequence)
}
 
do {
-   *sequence = dev_priv-fence_seq++;
+   *sequence = atomic_add_return(1, dev_priv-fence_seq);
} while (*sequence == 0);
 
if (!(fifo_state-capabilities  SVGA_FIFO_CAP_FENCE)) {
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
index d40086f..4d7cb53 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_irq.c
@@ -85,19 +85,12 @@ bool vmw_fence_signaled(struct vmw_private *dev_priv,
return true;
 
/**
-* Below is to signal stale fences that have wrapped.
-* First, block fence submission.
-*/
-
-   down_read(fifo_state-rwsem);
-
-   /**
 * Then check if the sequence is higher than what we've actually
 * emitted. Then the fence is stale and signaled.
 */
 
-   ret = ((dev_priv-fence_seq - sequence)  VMW_FENCE_WRAP);
-   up_read(fifo_state-rwsem);
+

[PATCH] drm/vmwgfx: Update the user-space interface.

2010-02-09 Thread Jakob Bornecrantz

From: Thomas Hellstrom thellst...@vmware.com

When time-based throttling is implemented, we need to bump minor.
When the old way of detecting scanout is removed, we need to bump major.
In the meantime, this change should not break existing user-space.

Signed-off-by: Thomas Hellstrom thellst...@vmware.com
Signed-off-by: Jakob Bornecrantz ja...@vmware.com
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c|6 ++
 drivers/gpu/drm/vmwgfx/vmwgfx_resource.c |5 +++--
 include/drm/vmwgfx_drm.h |   12 +---
 4 files changed, 21 insertions(+), 8 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
index 135be96..0eaf682 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
@@ -39,10 +39,10 @@
 #include ttm/ttm_execbuf_util.h
 #include ttm/ttm_module.h
 
-#define VMWGFX_DRIVER_DATE 20090724
+#define VMWGFX_DRIVER_DATE 20100118
 #define VMWGFX_DRIVER_MAJOR 0
-#define VMWGFX_DRIVER_MINOR 1
-#define VMWGFX_DRIVER_PATCHLEVEL 2
+#define VMWGFX_DRIVER_MINOR 9
+#define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x0010
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
 #define VMWGFX_MAX_RELOCATIONS 2048
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c
index 778851f..1c7a316 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_ioctl.c
@@ -48,6 +48,12 @@ int vmw_getparam_ioctl(struct drm_device *dev, void *data,
case DRM_VMW_PARAM_FIFO_OFFSET:
param-value = dev_priv-mmio_start;
break;
+   case DRM_VMW_PARAM_HW_CAPS:
+   param-value = dev_priv-capabilities;
+   break;
+   case DRM_VMW_PARAM_FIFO_CAPS:
+   param-value = dev_priv-fifo.capabilities;
+   break;
default:
DRM_ERROR(Illegal vmwgfx get param request: %d\n,
  param-param);
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
index c7efbd4..933e90d 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
@@ -610,9 +610,10 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
*data,
 */
srf-flags = ~SVGA3D_SURFACE_HINT_SCANOUT;
srf-scanout = true;
-   } else {
+   } else if (req-scanout)
+   srf-scanout = true;
+   else
srf-scanout = false;
-   }
 
if (srf-scanout 
srf-num_sizes == 1 
diff --git a/include/drm/vmwgfx_drm.h b/include/drm/vmwgfx_drm.h
index 2be7e12..dfaf3c2 100644
--- a/include/drm/vmwgfx_drm.h
+++ b/include/drm/vmwgfx_drm.h
@@ -68,7 +68,8 @@
 #define DRM_VMW_PARAM_NUM_FREE_STREAMS 1
 #define DRM_VMW_PARAM_3D   2
 #define DRM_VMW_PARAM_FIFO_OFFSET  3
-
+#define DRM_VMW_PARAM_HW_CAPS  4
+#define DRM_VMW_PARAM_FIFO_CAPS5
 
 /**
  * struct drm_vmw_getparam_arg
@@ -181,6 +182,8 @@ struct drm_vmw_context_arg {
  * The size of the array should equal the total number of mipmap levels.
  * @shareable: Boolean whether other clients (as identified by file 
descriptors)
  * may reference this surface.
+ * @scanout: Boolean whether the surface is intended to be used as a
+ * scanout.
  *
  * Input data to the DRM_VMW_CREATE_SURFACE Ioctl.
  * Output data from the DRM_VMW_REF_SURFACE Ioctl.
@@ -192,7 +195,7 @@ struct drm_vmw_surface_create_req {
uint32_t mip_levels[DRM_VMW_MAX_SURFACE_FACES];
uint64_t size_addr;
int32_t shareable;
-   uint32_t pad64;
+   int32_t scanout;
 };
 
 /**
@@ -295,6 +298,9 @@ union drm_vmw_surface_reference_arg {
  *
  * @commands: User-space address of a command buffer cast to an uint64_t.
  * @command-size: Size in bytes of the command buffer.
+ * @throttle-us: Sleep until software is less than @throttle_us
+ * microseconds ahead of hardware. The driver may round this value
+ * to the nearest kernel tick.
  * @fence_rep: User-space address of a struct drm_vmw_fence_rep cast to an
  * uint64_t.
  *
@@ -304,7 +310,7 @@ union drm_vmw_surface_reference_arg {
 struct drm_vmw_execbuf_arg {
uint64_t commands;
uint32_t command_size;
-   uint32_t pad64;
+   uint32_t throttle_us;
uint64_t fence_rep;
 };
 
-- 
1.6.0.4


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[PATCH] drm/vmwgfx: Support old hardware

2010-02-09 Thread Jakob Bornecrantz

Also included are overall modesetting improvements

Signed-off-by: Jakob Bornecrantz ja...@vmware.com
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c  |9 
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |5 ++
 drivers/gpu/drm/vmwgfx/vmwgfx_fb.c   |   81 --
 drivers/gpu/drm/vmwgfx/vmwgfx_fifo.c |   18 
 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c  |   68 +++-
 drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c  |   70 -
 6 files changed, 144 insertions(+), 107 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
index a6e8f68..5268af2 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
@@ -318,6 +318,15 @@ static int vmw_driver_load(struct drm_device *dev, 
unsigned long chipset)
goto out_err3;
}
 
+   /* need mmio memory to check for fifo pitchlock cap */
+   if (!(dev_priv-capabilities  SVGA_CAP_DISPLAY_TOPOLOGY) 
+   !(dev_priv-capabilities  SVGA_CAP_PITCHLOCK) 
+   !vmw_fifo_have_pitchlock(dev_priv)) {
+   ret = -ENOSYS;
+   DRM_ERROR(Hardware has no pitchlock\n);
+   goto out_err4;
+   }
+
dev_priv-tdev = ttm_object_device_init
(dev_priv-mem_global_ref.object, 12);
 
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
index 356dc93..fdcc1d6 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
@@ -179,6 +179,7 @@ struct vmw_private {
uint32_t vga_red_mask;
uint32_t vga_blue_mask;
uint32_t vga_green_mask;
+   uint32_t vga_pitchlock;
 
/*
 * Framebuffer info.
@@ -393,6 +394,7 @@ extern int vmw_fifo_send_fence(struct vmw_private *dev_priv,
 extern void vmw_fifo_ping_host(struct vmw_private *dev_priv, uint32_t reason);
 extern int vmw_fifo_mmap(struct file *filp, struct vm_area_struct *vma);
 extern bool vmw_fifo_have_3d(struct vmw_private *dev_priv);
+extern bool vmw_fifo_have_pitchlock(struct vmw_private *dev_priv);
 
 /**
  * TTM glue - vmwgfx_ttm_glue.c
@@ -466,6 +468,9 @@ void vmw_kms_cursor_snoop(struct vmw_surface *srf,
  struct ttm_object_file *tfile,
  struct ttm_buffer_object *bo,
  SVGA3dCmdHeader *header);
+void vmw_kms_write_svga(struct vmw_private *vmw_priv,
+   unsigned width, unsigned height, unsigned pitch,
+   unsigned bbp, unsigned depth);
 
 /**
  * Overlay control - vmwgfx_overlay.c
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
index 9822ee6..c1eae30 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_fb.c
@@ -135,16 +135,14 @@ static int vmw_fb_check_var(struct fb_var_screeninfo *var,
return -EINVAL;
}
 
-   /* without multimon its hard to resize */
-   if (!(vmw_priv-capabilities  SVGA_CAP_MULTIMON) 
-   (var-xres != par-max_width ||
-var-yres != par-max_height)) {
-   DRM_ERROR(Tried to resize, but we don't have multimon\n);
+   if (!(vmw_priv-capabilities  SVGA_CAP_DISPLAY_TOPOLOGY) 
+   (var-xoffset != 0 || var-yoffset != 0)) {
+   DRM_ERROR(Can not handle panning without display topology\n);
return -EINVAL;
}
 
-   if (var-xres  par-max_width ||
-   var-yres  par-max_height) {
+   if ((var-xoffset + var-xres)  par-max_width ||
+   (var-yoffset + var-yres)  par-max_height) {
DRM_ERROR(Requested geom can not fit in framebuffer\n);
return -EINVAL;
}
@@ -157,8 +155,8 @@ static int vmw_fb_set_par(struct fb_info *info)
struct vmw_fb_par *par = info-par;
struct vmw_private *vmw_priv = par-vmw_priv;
 
-   if (vmw_priv-capabilities  SVGA_CAP_MULTIMON) {
-   vmw_write(vmw_priv, SVGA_REG_NUM_GUEST_DISPLAYS, 1);
+   if (vmw_priv-capabilities  SVGA_CAP_DISPLAY_TOPOLOGY) {
+   vmw_write(vmw_priv, SVGA_REG_ENABLE, 0);
vmw_write(vmw_priv, SVGA_REG_DISPLAY_ID, 0);
vmw_write(vmw_priv, SVGA_REG_DISPLAY_IS_PRIMARY, true);
vmw_write(vmw_priv, SVGA_REG_DISPLAY_POSITION_X, 0);
@@ -167,18 +165,11 @@ static int vmw_fb_set_par(struct fb_info *info)
vmw_write(vmw_priv, SVGA_REG_DISPLAY_HEIGHT, 0);
vmw_write(vmw_priv, SVGA_REG_DISPLAY_ID, SVGA_ID_INVALID);
 
-   vmw_write(vmw_priv, SVGA_REG_ENABLE, 1);
-   vmw_write(vmw_priv, SVGA_REG_WIDTH, par-max_width);
-   vmw_write(vmw_priv, SVGA_REG_HEIGHT, par-max_height);
-   vmw_write(vmw_priv, SVGA_REG_BITS_PER_PIXEL, par-bpp);
-   vmw_write(vmw_priv, SVGA_REG_DEPTH, par-depth);
-   vmw_write(vmw_priv, SVGA_REG_RED_MASK, 0x00ff);
-

[PATCH] drm/vmwgfx: Bump major and drop scanout flag compat

2010-02-09 Thread Jakob Bornecrantz

Even if this bumps the version to 1 it does not mean the driver is
out of staging. From what we know this is the last backwards
incompatible change to the driver.

Signed-off-by: Jakob Bornecrantz ja...@vmware.com
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_resource.c |   17 +
 2 files changed, 4 insertions(+), 19 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
index 9c89868..356dc93 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
@@ -39,9 +39,9 @@
 #include ttm/ttm_execbuf_util.h
 #include ttm/ttm_module.h
 
-#define VMWGFX_DRIVER_DATE 20100118
-#define VMWGFX_DRIVER_MAJOR 0
-#define VMWGFX_DRIVER_MINOR 9
+#define VMWGFX_DRIVER_DATE 20100209
+#define VMWGFX_DRIVER_MAJOR 1
+#define VMWGFX_DRIVER_MINOR 0
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x0010
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
index 933e90d..f8fbbc6 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
@@ -35,11 +35,6 @@
 #define VMW_RES_SURFACE ttm_driver_type1
 #define VMW_RES_STREAM ttm_driver_type2
 
-/* XXX: This isn't a real hardware flag, but just a hack for kernel to
- * know about primary surfaces. Find a better way to accomplish this.
- */
-#define SVGA3D_SURFACE_HINT_SCANOUT (1  9)
-
 struct vmw_user_context {
struct ttm_base_object base;
struct vmw_resource res;
@@ -579,6 +574,7 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
*data,
 
srf-flags = req-flags;
srf-format = req-format;
+   srf-scanout = req-scanout;
memcpy(srf-mip_levels, req-mip_levels, sizeof(srf-mip_levels));
srf-num_sizes = 0;
for (i = 0; i  DRM_VMW_MAX_SURFACE_FACES; ++i)
@@ -604,17 +600,6 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
*data,
if (unlikely(ret != 0))
goto out_err1;
 
-   if (srf-flags  SVGA3D_SURFACE_HINT_SCANOUT) {
-   /* we should not send this flag down to hardware since
-* its not a official one
-*/
-   srf-flags = ~SVGA3D_SURFACE_HINT_SCANOUT;
-   srf-scanout = true;
-   } else if (req-scanout)
-   srf-scanout = true;
-   else
-   srf-scanout = false;
-
if (srf-scanout 
srf-num_sizes == 1 
srf-sizes[0].width == 64 
-- 
1.6.0.4


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Bugme-new] [Bug 15248] New: KMS broken on Intel 855GM broken with 2.6.32/33

2010-02-09 Thread Jesse Barnes

On Tue, 9 Feb 2010 13:23:50 +0100
Rafael J. Wysocki r...@sisk.pl wrote:

 On Tuesday 09 February 2010, Andrew Morton wrote:
  On Sun, 7 Feb 2010 09:59:06 GMT
  bugzilla-dae...@bugzilla.kernel.org wrote:
  
   http://bugzilla.kernel.org/show_bug.cgi?id=15248
  
  DRI/KMS regression #1,987,776
 
 Added, CCing dri-devel and the i915 maintainers.
 

Hey now, I only count 10 that look KMS related, that's a lot fewer than
1,987,776.  Better yet, 6 or so have fixes now, and the other ones are
getting looked at.  So there.

-- 
Jesse Barnes, Intel Open Source Technology Center

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [PATCH] drm/vmwgfx: Bump major and drop scanout flag compat

2010-02-09 Thread Thomas Hellstrom

Jakob Bornecrantz wrote:
 Even if this bumps the version to 1 it does not mean the driver is
 out of staging. From what we know this is the last backwards
 incompatible change to the driver.

 Signed-off-by: Jakob Bornecrantz ja...@vmware.com
 ---
  drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |6 +++---
  drivers/gpu/drm/vmwgfx/vmwgfx_resource.c |   17 +
  2 files changed, 4 insertions(+), 19 deletions(-)

 diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
 b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
 index 9c89868..356dc93 100644
 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
 +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
 @@ -39,9 +39,9 @@
  #include ttm/ttm_execbuf_util.h
  #include ttm/ttm_module.h
  
 -#define VMWGFX_DRIVER_DATE 20100118
 -#define VMWGFX_DRIVER_MAJOR 0
 -#define VMWGFX_DRIVER_MINOR 9
 +#define VMWGFX_DRIVER_DATE 20100209
 +#define VMWGFX_DRIVER_MAJOR 1
 +#define VMWGFX_DRIVER_MINOR 0
  #define VMWGFX_DRIVER_PATCHLEVEL 0
  #define VMWGFX_FILE_PAGE_OFFSET 0x0010
  #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
 diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c 
 b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
 index 933e90d..f8fbbc6 100644
 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
 +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
 @@ -35,11 +35,6 @@
  #define VMW_RES_SURFACE ttm_driver_type1
  #define VMW_RES_STREAM ttm_driver_type2
  
 -/* XXX: This isn't a real hardware flag, but just a hack for kernel to
 - * know about primary surfaces. Find a better way to accomplish this.
 - */
 -#define SVGA3D_SURFACE_HINT_SCANOUT (1  9)
 -
  struct vmw_user_context {
   struct ttm_base_object base;
   struct vmw_resource res;
 @@ -579,6 +574,7 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
 *data,
  
   srf-flags = req-flags;
   srf-format = req-format;
 + srf-scanout = req-scanout;
   memcpy(srf-mip_levels, req-mip_levels, sizeof(srf-mip_levels));
   srf-num_sizes = 0;
   for (i = 0; i  DRM_VMW_MAX_SURFACE_FACES; ++i)
 @@ -604,17 +600,6 @@ int vmw_surface_define_ioctl(struct drm_device *dev, 
 void *data,
   if (unlikely(ret != 0))
   goto out_err1;
  
 - if (srf-flags  SVGA3D_SURFACE_HINT_SCANOUT) {
 - /* we should not send this flag down to hardware since
 -  * its not a official one
 -  */
 - srf-flags = ~SVGA3D_SURFACE_HINT_SCANOUT;
 - srf-scanout = true;
 - } else if (req-scanout)
 - srf-scanout = true;
 - else
 - srf-scanout = false;
 -
   if (srf-scanout 
   srf-num_sizes == 1 
   srf-sizes[0].width == 64 
   

Nack. There are some more minor pending changes before we bump. I'll 
resend shortly.

/Thomas


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26496] New: OpenGL does not work on Radeon 9600 (r300)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26496

   Summary: OpenGL does not work on Radeon 9600 (r300)
   Product: DRI
   Version: XOrg 6.7.0
  Platform: PowerPC
OS/Version: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: benja...@sipsolutions.net


I have a PowerBook G4 with an RV350 [Mobility Radeon 9600 M10] graphics card.
For quite some time now I am seeing rendering issues in OpenGL using
application. Attaching a screenshot of neverball when it is started.

This is a debian testing machine with the following package versions:
xserver-xorg 1:7.5+3
xserver-xorg-video-radeon1:6.12.4-3
libdrm-radeon1   2.4.17-1

I am happy to provide more information if neccessary.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26496] OpenGL does not work on Radeon 9600 (r300)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26496





--- Comment #1 from Benjamin Berg benja...@sipsolutions.net  2010-02-09 
12:12:36 PST ---
Created an attachment (id=33196)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=33196)
neverball on the start screen after running a bit


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[PATCH] drm/vmwgfx: Drop scanout flag compat and add execbuf ioctl parameter members. Bumps major.

2010-02-09 Thread Thomas Hellstrom

From: Jakob Bornecrantz ja...@vmware.com

Even if this bumps the version to 1 it does not mean the driver is
out of staging. From what we know this is the last backwards
incompatible change to the driver.

Signed-off-by: Jakob Bornecrantz ja...@vmware.com
Signed-off-by: Thomas Hellstrom thellst...@vmware.com
---
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h  |6 +++---
 drivers/gpu/drm/vmwgfx/vmwgfx_resource.c |   17 +
 include/drm/vmwgfx_drm.h |8 
 3 files changed, 12 insertions(+), 19 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h 
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
index 9c89868..356dc93 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
@@ -39,9 +39,9 @@
 #include ttm/ttm_execbuf_util.h
 #include ttm/ttm_module.h
 
-#define VMWGFX_DRIVER_DATE 20100118
-#define VMWGFX_DRIVER_MAJOR 0
-#define VMWGFX_DRIVER_MINOR 9
+#define VMWGFX_DRIVER_DATE 20100209
+#define VMWGFX_DRIVER_MAJOR 1
+#define VMWGFX_DRIVER_MINOR 0
 #define VMWGFX_DRIVER_PATCHLEVEL 0
 #define VMWGFX_FILE_PAGE_OFFSET 0x0010
 #define VMWGFX_FIFO_STATIC_SIZE (1024*1024)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c 
b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
index 933e90d..f8fbbc6 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_resource.c
@@ -35,11 +35,6 @@
 #define VMW_RES_SURFACE ttm_driver_type1
 #define VMW_RES_STREAM ttm_driver_type2
 
-/* XXX: This isn't a real hardware flag, but just a hack for kernel to
- * know about primary surfaces. Find a better way to accomplish this.
- */
-#define SVGA3D_SURFACE_HINT_SCANOUT (1  9)
-
 struct vmw_user_context {
struct ttm_base_object base;
struct vmw_resource res;
@@ -579,6 +574,7 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
*data,
 
srf-flags = req-flags;
srf-format = req-format;
+   srf-scanout = req-scanout;
memcpy(srf-mip_levels, req-mip_levels, sizeof(srf-mip_levels));
srf-num_sizes = 0;
for (i = 0; i  DRM_VMW_MAX_SURFACE_FACES; ++i)
@@ -604,17 +600,6 @@ int vmw_surface_define_ioctl(struct drm_device *dev, void 
*data,
if (unlikely(ret != 0))
goto out_err1;
 
-   if (srf-flags  SVGA3D_SURFACE_HINT_SCANOUT) {
-   /* we should not send this flag down to hardware since
-* its not a official one
-*/
-   srf-flags = ~SVGA3D_SURFACE_HINT_SCANOUT;
-   srf-scanout = true;
-   } else if (req-scanout)
-   srf-scanout = true;
-   else
-   srf-scanout = false;
-
if (srf-scanout 
srf-num_sizes == 1 
srf-sizes[0].width == 64 
diff --git a/include/drm/vmwgfx_drm.h b/include/drm/vmwgfx_drm.h
index dfaf3c2..c7645f4 100644
--- a/include/drm/vmwgfx_drm.h
+++ b/include/drm/vmwgfx_drm.h
@@ -303,15 +303,23 @@ union drm_vmw_surface_reference_arg {
  * to the nearest kernel tick.
  * @fence_rep: User-space address of a struct drm_vmw_fence_rep cast to an
  * uint64_t.
+ * @version: Allows expanding the execbuf ioctl parameters without breaking
+ * backwards compatibility, since user-space will always tell the kernel
+ * which version it uses.
+ * @flags: Execbuf flags. None currently.
  *
  * Argument to the DRM_VMW_EXECBUF Ioctl.
  */
 
+#define DRM_VMW_EXECBUF_VERSION 0
+
 struct drm_vmw_execbuf_arg {
uint64_t commands;
uint32_t command_size;
uint32_t throttle_us;
uint64_t fence_rep;
+uint32_t version;
+uint32_t flags;
 };
 
 /**
-- 
1.6.2.5


--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15151] Black screen after loading nouveau module

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15151


Marcin Slusarz marcin.slus...@gmail.com changed:

   What|Removed |Added

  Attachment #24883|0   |1
is obsolete||




--- Comment #15 from Marcin Slusarz marcin.slus...@gmail.com  2010-02-09 
20:37:09 ---
Created an attachment (id=24977)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=24977)
efifb fix v2

i just noticed one more bug, please retest the new patch

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 15166] Changing brightness of backlight freezes kernel with radeon kms enabled.

2010-02-09 Thread bugzilla-daemon

http://bugzilla.kernel.org/show_bug.cgi?id=15166





--- Comment #22 from Manuel Ullmann ullman.b...@gmx.de  2010-02-09 20:58:17 
---
Created an attachment (id=24980)
 -- (http://bugzilla.kernel.org/attachment.cgi?id=24980)
syslog-ng output of an isuue caused by BIOS.

@Alex Deucher:

You mentioned earlier some 'scratch reg bits'. What are they doing? How could
they fix issues specific to certain systems like the Compaq 6735b series?
Your patch at
http://people.freedesktop.org/~agd5f/0001-drm-radeon-kms-add-additional-safe-regs-for-r4xx-rs.patch
seems to be related to those bits, but it is specific to some graphic chips.


I have experienced, that waking up from S3 or S4 can indeed change the
brightness with kms. As mentioned in Comment 12, the brightness uninitialized
until it is changed. /sys/class/backlight/acpi_video?/backlight has the value
0, although the backlight has full brightness, which should be 24. When
hibernate-script reinitializes the backlight, it is switched to its lowest
brightness. So I can choose now between the highest and lowest brightness. But
nevertheless the main issue, that the system freezes after certain amount of
inactivity, remains.

I understand, that the firmware is not likely to be updated and that instead
the kernel framework around it maybe has to be fixed. Of course this could be
also BIOS-related, as I had already an issue, which was caused by an error in
BIOS with this notebook (see attachement). But as this Bug is not
OS-independent, I doubt that it would be fixed ever.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26496] OpenGL does not work on Radeon 9600 (r300)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26496


Alex Deucher ag...@yahoo.com changed:

   What|Removed |Added

  Component|DRM/Radeon  |Drivers/DRI/r300
Product|DRI |Mesa
Version|XOrg 6.7.0  |unspecified




--- Comment #2 from Alex Deucher ag...@yahoo.com  2010-02-09 13:18:27 PST ---
What version of mesa are you using?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26471] Missing background graphics/texture in frogatto with R600 (RV670)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26471





--- Comment #10 from Andrius Štikonas stiko...@gmail.com  2010-02-09 13:34:41 
PST ---
Frogatto started working after revision 1713

r1713: Integrated the rectangle rotation code into the blitting routines to
actually be used when an object is to be rotated.

So this bug can be caused by broken blitting on r600.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26471] Missing background graphics/texture in frogatto with R600 (RV670)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26471





--- Comment #11 from Andrius Štikonas stiko...@gmail.com  2010-02-09 13:39:21 
PST ---
Created an attachment (id=33197)
 -- (http://bugs.freedesktop.org/attachment.cgi?id=33197)
Frogatto intro scene screenshot r1713

The diff of the revision that broken Frogatto even worse.

http://code.google.com/p/frogatto/source/detail?r=1713#


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

[Bug 26471] Missing background graphics/texture in frogatto with R600 (RV670)

2010-02-09 Thread bugzilla-daemon

http://bugs.freedesktop.org/show_bug.cgi?id=26471





--- Comment #12 from Alex Deucher ag...@yahoo.com  2010-02-09 13:45:38 PST ---
(In reply to comment #10)
 Frogatto started working after revision 1713
 
 r1713: Integrated the rectangle rotation code into the blitting routines to
 actually be used when an object is to be rotated.
 
 So this bug can be caused by broken blitting on r600.
 

Sounds like an app bug if it's fixed in a newer version of the app.  The r600
driver in mesa 7.6 and 7.7 doesn't accelerate CopyTex(Sub)Image (which is what
the 'blit' code in the r600 driver does), only mesa master does.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Bugme-new] [Bug 15259] New: Corruption with OpenGL since Intel's big DRM push on i945

2010-02-09 Thread Rafael J. Wysocki

On Tuesday 09 February 2010, Andrew Morton wrote:
 On Mon, 8 Feb 2010 13:19:12 GMT
 bugzilla-dae...@bugzilla.kernel.org wrote:
 
  http://bugzilla.kernel.org/show_bug.cgi?id=15259
 
 1,987,777 :)

Added, CCing dri-devel and Eric.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

40 matches

Mail list logo