http://bugs.freedesktop.org/show_bug.cgi?id=26686
Chris Wilson ch...@chris-wilson.co.uk changed:
What|Removed |Added
AssignedTo|ch...@chris-wilson.co.uk|dri-
http://bugzilla.kernel.org/show_bug.cgi?id=15276
--- Comment #37 from Michał Witkowski ne...@o2.pl 2010-02-22 11:57:12 ---
I've just had a similar crash to the one described above in Inkscape drawing
some Bezier curves with KWin's compositing turned _off_. This crashing is a
real problem in
http://bugzilla.kernel.org/show_bug.cgi?id=15276
Jérôme Glisse gli...@freedesktop.org changed:
What|Removed |Added
Status|NEEDINFO|ASSIGNED
---
http://bugzilla.kernel.org/show_bug.cgi?id=15276
--- Comment #39 from Jérôme Glisse gli...@freedesktop.org 2010-02-22
12:22:26 ---
How best thing you can do is try to find some automatic test case. For instance
using gtkperf or any other program that can run automaticly and will trigger
the
http://bugzilla.kernel.org/show_bug.cgi?id=14535
Julien Cristau jcris...@debian.org changed:
What|Removed |Added
CC||jcris...@debian.org
http://bugs.freedesktop.org/show_bug.cgi?id=25063
JP Rosevear j...@novell.com changed:
What|Removed |Added
Status Whiteboard||bloody vpn
--
http://bugs.freedesktop.org/show_bug.cgi?id=26686
--- Comment #5 from Ruslan b7.10110...@gmail.com 2010-02-22 07:17:22 PST ---
I tried to comment out this line:
bo_gem-tiling_mode = set_tiling.tiling_mode;
and now things seem to work. I.e., this statement:
it overwrites the input
2010/2/20 Rafał Miłecki zaj...@gmail.com:
We kept pointers to requested and current clock modes in every power state.
That was useless, more /global/ pointers in power struct are enough.
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
As discussed with Alex we will simplify pointers only,
2010/2/21 Rafał Miłecki zaj...@gmail.com:
AtomBIOS tables on non-mobility GPU do not contain POWERSAVE/BATTERY.
Looks good. At some point we may want to tweak the selection algo a
bit. It looks like the lowest power states tend to have the
SINGLE_DISPLAY_ONLY flag set (which we'd have to
http://bugs.freedesktop.org/show_bug.cgi?id=25063
Daniel Stone dan...@fooishbar.org changed:
What|Removed |Added
Status Whiteboard|bloody vpn |
--- Comment #7
On Mon, Feb 22, 2010 at 08:17:31AM -0700, Brian Paul wrote:
On Sun, Feb 21, 2010 at 5:54 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Sun, Feb 21, 2010 at 2:33 PM, Keith Packard kei...@keithp.com wrote:
The bash 'cd' command tends to emit random stuff to stdout when the
CDPATH variable
http://bugs.freedesktop.org/show_bug.cgi?id=26686
--- Comment #6 from Ruslan b7.10110...@gmail.com 2010-02-22 08:10:42 PST ---
I added perror() before 'return -errno;' to see what error doesn't report
tiling mode, and got Invalid argument, i.e. EINVAL. Then i found this in
On Mon, Feb 22, 2010 at 7:17 AM, Brian Paul brian.e.p...@gmail.com wrote:
On Sun, Feb 21, 2010 at 5:54 PM, Dan Nicholson dbn.li...@gmail.com wrote:
On Sun, Feb 21, 2010 at 2:33 PM, Keith Packard kei...@keithp.com wrote:
The bash 'cd' command tends to emit random stuff to stdout when the
CDPATH
http://bugs.freedesktop.org/show_bug.cgi?id=23234
Alex Deucher ag...@yahoo.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
This add the support for the new fault callback and also the
infrastructure for supporting unmappable VRAM.
V2 validate BO with no_wait = true
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/radeon/radeon_ttm.c | 99 ++-
1 files changed, 98
Thomas i think i addressed your concern here, the ttm_bo_validate
didn't needed a new argument or i did not understand what was
necessary beside no_wait. In this patchset we check the value
of callback in case of EBUSY (call set_need_resched) or ERESTARTSYS
we return VM_FAULT_NOPAGE.
For the
On fault the driver is given the opportunity to perform any operation
it sees fit in order to place the buffer into a CPU visible area of
memory. This patch doesn't break TTM users, nouveau, vmwgfx and radeon
should keep working properly. Future patch will take advantage of this
infrastructure and
This add the support for the new fault callback, does change anything
from driver point of view.
Improvement: store the aperture base in a variable so that we don't
call a function to get it on each fault.
Patch hasn't been tested.
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
This add the support for the new fault callback, does change anything
from driver point of view, thought it should allow nouveau to add
support for unmappable VRAM.
Improvement: store the aperture base in a variable so that we don't
call a function to get it on each fault.
Patch hasn't been
On fault the driver is given the opportunity to perform any operation
it sees fit in order to place the buffer into a CPU visible area of
memory. This patch doesn't break TTM users, nouveau, vmwgfx and radeon
should keep working properly. Future patch will take advantage of this
infrastructure and
All TTM driver have been converted to new io_mem_reserve/free
interface which allow driver to choose and return proper io
base, offset to core TTM for ioremapping if necessary. This
patch remove what is now deadcode.
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
This add the support for the new fault callback and also the
infrastructure for supporting unmappable VRAM.
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/radeon/radeon_ttm.c | 99 ++-
1 files changed, 98 insertions(+), 1 deletions(-)
diff
This isn't needed anymore with the new TTM fault callback
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/radeon/radeon_ttm.c | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c
This isn't needed anymore with the new TTM fault callback
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c
This isn't needed anymore with the new TTM fault callback
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/nouveau/nouveau_bo.c | 11 ---
1 files changed, 0 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c
All TTM driver have been converted to new io_mem_reserve/free
interface which allow driver to choose and return proper io
base, offset to core TTM for ioremapping if necessary. This
patch remove what is now deadcode.
V2 adapt to match with change in first patch of the patchset
Signed-off-by:
This patch enable the use of unmappable VRAM thanks to
previous TTM infrastructure change.
Signed-off-by: Jerome Glisse jgli...@redhat.com
---
drivers/gpu/drm/radeon/evergreen.c |5 -
drivers/gpu/drm/radeon/r100.c |5 -
drivers/gpu/drm/radeon/r600.c |5 -
Jerome Glisse wrote:
Thomas i think i addressed your concern here, the ttm_bo_validate
didn't needed a new argument or i did not understand what was
necessary beside no_wait. In this patchset we check the value
of callback in case of EBUSY (call set_need_resched) or ERESTARTSYS
we return
Please commit to both master and mesa_7_7_branch. Thanks.
mesa_7_7_branch doesn't use 'cd' in mklib.
--
keith.pack...@intel.com
pgpa1vIunw8Ui.pgp
Description: PGP signature
--
Download Intel#174; Parallel Studio
On Mon, Feb 22, 2010 at 06:30:24PM +0100, Thomas Hellstrom wrote:
Jerome Glisse wrote:
Thomas i think i addressed your concern here, the ttm_bo_validate
didn't needed a new argument or i did not understand what was
necessary beside no_wait. In this patchset we check the value
of callback
http://bugs.freedesktop.org/show_bug.cgi?id=26430
--- Comment #7 from Scott Moreau ore...@gmail.com 2010-02-22 11:45:52 PST ---
Created an attachment (id=33498)
-- (http://bugs.freedesktop.org/attachment.cgi?id=33498)
dmesg with drm.debug=15
This is booting latest drm-radeon-testing kernel
http://bugs.freedesktop.org/show_bug.cgi?id=26430
--- Comment #8 from Scott Moreau ore...@gmail.com 2010-02-22 11:47:54 PST ---
I am using latest (45fa67f404bb08ef4b04504766753c28e354ecb2 [rfc]
drm/radeon/kms: pm debugging check for vbl.) drm-radeon-testing kernel on rv350
and I have a
Jerome Glisse wrote:
On Mon, Feb 22, 2010 at 06:30:24PM +0100, Thomas Hellstrom wrote:
Jerome Glisse wrote:
Thomas i think i addressed your concern here, the ttm_bo_validate
didn't needed a new argument or i did not understand what was
necessary beside no_wait. In this patchset we
http://bugzilla.kernel.org/show_bug.cgi?id=15328
Rafael J. Wysocki r...@sisk.pl changed:
What|Removed |Added
Status|NEW |RESOLVED
http://bugzilla.kernel.org/show_bug.cgi?id=15293
--- Comment #20 from Vi0L0 vi0l...@gmail.com 2010-02-22 21:45:55 ---
With midori browser flash seems to work much faster.
In fact i've got no lags on our vimeo flash video example when using midori...
So maybe it's not kms problem at all(?)
http://bugs.freedesktop.org/show_bug.cgi?id=26708
Summary: libdrm-intel leaks memory when resizing window
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority:
it's not kms problem at all(?)
Todays (20100222) git of xf86-video-ati libdrm glproto and mesa.
Yes, I can confirm. In midori 0.2.3 there is no lag. Firefox, Chromium and
Arora still laggy, though. And the video is not laggy while using latest
xf86-video-intel on my 4500MHD.
--
Configure
On Monday 22 February 2010, you wrote:
On Mon, 22 Feb 2010, Rafael J. Wysocki wrote:
Here's what I got:
[3.349334] PM: Resume from disk failed.
[3.350060] Magic number: 0:141:321
[3.352583] hash matches drivers/base/power/main.c:477
[3.355144] tty tty46:
http://bugs.freedesktop.org/show_bug.cgi?id=25142
--- Comment #27 from Allen Walker walkerallen...@googlemail.com 2010-02-22
15:16:22 PST ---
(In reply to comment #26)
(In reply to comment #25)
I finally got KMS working with thursday's mesa and xf86-video-ati having the
same issue:
http://bugzilla.kernel.org/show_bug.cgi?id=14535
--- Comment #22 from Dave Airlie airl...@linux.ie 2010-02-23 00:35:20 ---
is anyone who is seeing this using page flipping?
I'm still not having any luck here reproducing it on an T42 with mesa 7.6.1
from the branch, 2.6.32.3 kernel
--
drmCheckModesettingSupported did erronously report that
kernel doesn't have modesetting support if kernel module
wasn't preloaded.
To make KMS checking load kernel module before retring
drmCheckModuleAndModesettingSupported takes module_name
as parameter. If drm module isn't loaded drm tries to
http://bugzilla.kernel.org/show_bug.cgi?id=14535
--- Comment #23 from Dave Airlie airl...@linux.ie 2010-02-23 01:32:29 ---
It would be really nice if the people seeing hangs and crashes that aren't
(a) filesystem corruption
(b) low memory corruption
could not talk about it any more.
Then
This prevents ddx from selecting UMS if KMS is enabled but
kernel module is not loaded before X.
Signed-off-by: Pauli Nieminen suok...@gmail.com
---
configure.ac |3 +++
src/radeon_probe.c |6 ++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/configure.ac
http://bugs.freedesktop.org/show_bug.cgi?id=26710
Summary: wine make test segfaults in r600_dri.so
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
On Sat, Feb 20, 2010 at 12:22 PM, Maarten Maathuis madman2...@gmail.com wrote:
- Without this change I get a general protection fault.
- Also use PTR_ERR where applicable.
I just want to make sure I understand, but really the only bit of this
patch that matters is:
@@ -556,9 +559,10 @@ int
Just nouveau/vmwgfx changes, the nouveau ones fix nouveau to work
on a range of IGP chipsets, mostly seen as ION or in Apple laptops,
Without these changes there is a chance of memory corruption on the low
pages since the GPU tables are setup different to every other nvidia in
history.
Dave.
On Sat, Feb 20, 2010 at 18:18, Bruno Prémont wrote:
drivers/video/bf54x-lq043fb.c | 2 +-
drivers/video/bfin-t350mcqb-fb.c | 2 +-
Acked-by: Mike Frysinger vap...@gentoo.org
-mike
H,
I am using linux-2.6.33-rc8 with my laptop. This one has a DVI-D port that
I use (with an adapter) to connect to my HDTV screen. I want to get the
full 1920x1080 (1080p) resolution.
In X, I disable loading of DRI module as X is unstable under KDE4 with DRI1 or
DRI2 enabled.
1.
Are there
2010/2/22 Hendrik Sattler p...@hendrik-sattler.de:
2.
xrandr only offers 1080p only if the TV is connected before booting, else
only 1366x768 is available. So 1080p is technically possible.
Please boot without TV, then execute and provide output of xrandr --verbose
3.
My TV accepts
http://bugzilla.kernel.org/show_bug.cgi?id=13170
Zhang Rui rui.zh...@intel.com changed:
What|Removed |Added
Component|Config-Tables |Video(DRI - non Intel)
50 matches
Mail list logo