[Bug 24066] On the Rain-Slick Precipice of Darkness, Episode One crashes before first starting screen

https://bugs.freedesktop.org/show_bug.cgi?id=24066 --- Comment #11 from Agra labi...@gmail.com --- Hello, I am experiencing the same wireframe issue on the steam version. Happens in character creation. Clicking anything lets me know that display driver is not responding and craches. Win7x64, ATI

Re: [RFC 1/21] Add VIA DRM driver

commit 1fcf23d361375645d586756d126b436796ba4fba Author: James Simmons jsimm...@infradead.org Date: Sat Jun 8 09:31:57 2013 -0400 via: New KMS ioctls and hardware to support. Add new VIA pci ids to support newer hardware. Cleanup userspace api structs to remove kernel types

[git pull] drm fixes

Hi Linus, just some GMA500 memory leaks and i915 regression fix due to regression fix. Dave. The following changes since commit ab0296319a8cb970f4e42659472bb40fbfae3e56: Merge tag 'spi-v3.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (2013-06-10 13:28:39 -0700)

Re: [PATCH v4 0/4] add mutex wait/wound/style style locks

Op 28-05-13 16:48, Maarten Lankhorst schreef: Version 4 already? Small api changes since v3: - Remove ww_mutex_unlock_single and ww_mutex_lock_single. - Rename ww_mutex_trylock_single to ww_mutex_trylock. - Remove separate implementations of ww_mutex_lock_slow*, normal functions can be

[PATCH] drm: Don't pass negative delta to ktime_sub_ns()

From: Michel Dänzer michel.daen...@amd.com It takes an unsigned value. This happens not to blow up on 64-bit architectures, but it does on 32-bit, causing drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus timestamps for vblank events. Which in turn causes e.g. gnome-shell to hang

Re: [PATCH] radeon: Fix a false positive lockup after 10s of inactivity

On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: If the device is idle for over ten seconds, then the next attempt to do anything can race with the lockup detector and cause a bogus lockup to be detected. Oddly, the situation is well-described in the lockup detector's comments and

Re: [PATCH 2/6] gpu: host1x: Fix syncpoint wait return value

On 11.06.2013 15:09, Daniel Vetter wrote: Maybe it wasn't clear, but -EAGAIN does _not_ resubmit work. -EAGAIN is used to restart the ioctl if we had to kick a thread (to make sure it doesn't hold any locks), e.g. for a blocking wait on oustanding rendering. The codepaths taken work exactly as

Re: [PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, Jun 12, 2013 at 11:58:44AM +0200, Michel Dänzer wrote: From: Michel Dänzer michel.daen...@amd.com It takes an unsigned value. This happens not to blow up on 64-bit architectures, but it does on 32-bit, causing drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus

Re: [PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, 2013-06-12 at 11:58 +0200, Michel Dänzer wrote: From: Michel Dänzer michel.daen...@amd.com It takes an unsigned value. This happens not to blow up on 64-bit architectures, but it does on 32-bit, causing drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus timestamps

Re: [PATCH 2/6] gpu: host1x: Fix syncpoint wait return value

On Wed, Jun 12, 2013 at 12:28 PM, Terje Bergström tbergst...@nvidia.com wrote: On 11.06.2013 15:09, Daniel Vetter wrote: Maybe it wasn't clear, but -EAGAIN does _not_ resubmit work. -EAGAIN is used to restart the ioctl if we had to kick a thread (to make sure it doesn't hold any locks), e.g.

Re: [PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, Jun 12, 2013 at 11:48:13AM +0100, Chris Wilson wrote: On Wed, Jun 12, 2013 at 11:58:44AM +0200, Michel Dänzer wrote: From: Michel Dänzer michel.daen...@amd.com It takes an unsigned value. This happens not to blow up on 64-bit architectures, but it does on 32-bit, causing

Re: [PATCH] radeon: Fix a false positive lockup after 10s of inactivity

Am 12.06.2013 12:26, schrieb Michel Dänzer: On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: If the device is idle for over ten seconds, then the next attempt to do anything can race with the lockup detector and cause a bogus lockup to be detected. Oddly, the situation is

[PATCH 0/3] drm/cma: use prim helpers instead GEM CMA specific dma_buf functionality

Hi, GEM CMA supports dma_buf but it needs GEM CMA specific functionality for dma_buf. We can use prime helpers for dma_buf by commit 89177644a7b6306e6084a89eab7e290f4bfef397 drm: add prime helpers, so this patchset is to replace from using GEM CMA specific functions to using prime helpers.

[PATCH 1/3] drm: add mmap function to prime helpers

This adds to call low-level mmap() from prime helpers. Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com --- drivers/gpu/drm/drm_prime.c | 5 - include/drm/drmP.h | 2 ++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_prime.c

[PATCH 2/3] drm/cma: add low-level hook functions to use prime helpers

Instead of using the dma_buf functionality for GEM CMA, we can use prime helpers if we can provide low-level hook functions for GEM CMA. Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com --- drivers/gpu/drm/drm_gem_cma_helper.c | 76

[PATCH 3/3] drm/cma: remove GEM CMA specific dma_buf functionality

We can use prime helpers instead. Signed-off-by: Joonyoung Shim jy0922.s...@samsung.com --- drivers/gpu/drm/drm_gem_cma_helper.c | 283 --- include/drm/drm_gem_cma_helper.h | 6 - 2 files changed, 289 deletions(-) diff --git

Re: [PATCH 0/3] drm/cma: use prim helpers instead GEM CMA specific dma_buf functionality

Hi Joonyoung, Thank you for the patches. I'll try to review and test them next week. On Wednesday 12 June 2013 22:16:14 Joonyoung Shim wrote: Hi, GEM CMA supports dma_buf but it needs GEM CMA specific functionality for dma_buf. We can use prime helpers for dma_buf by commit

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Tue, Jun 11, 2013 at 09:48:57AM +1000, Dave Airlie wrote: On Tue, Jun 11, 2013 at 9:36 AM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Tue, Jun 11, 2013 at 09:24:16AM +1000, Dave Airlie

Re: [PATCH] radeon: Fix a false positive lockup after 10s of inactivity

On Wed, Jun 12, 2013 at 6:26 AM, Michel Dänzer mic...@daenzer.net wrote: On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: If the device is idle for over ten seconds, then the next attempt to do anything can race with the lockup detector and cause a bogus lockup to be detected.

Re: [PATCH] drm/mgag200: Don't do full cleanup if mgag200_device_init fails

On Wed, Jun 05 2013, Christopher Harvey char...@matrox.com wrote: Running mgag200_driver_unload when the driver init fails early on causes functions like drm_mode_config_cleanup to be called. The problem is, drm_mode_config_cleanup crashes because the corresponding init hasn't happend yet.

Re: [PATCH] drm/mgag200: Hardware cursor support

On Wed, Jun 05 2013, Christopher Harvey char...@matrox.com wrote: G200 cards support, at best, 16 colour palleted images for the cursor so we do a conversion in the cursor_set function, and reject cursors with more than 16 colours, or cursors with partial transparency. Xorg falls back

[PATCH 1/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

This code was ported from the old xorg mga driver. These limits were implemented as a solution to a number of problems that were seen. These problems were linked to the bandwidth limitations of the g200e series. Signed-off-by: Julia Lemire jlem...@matrox.com ---

[PATCH 0/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

At the larger resolutions, the g200e series sometimes struggles with maintaining a proper output. Problems like flickering or black bands appearing on screen can occur. In order to avoid this, limitations regarding resolutions and bandwidth have been added for the different variations of the

[Bug 64257] RS880 issues with r600-llvm-compiler

https://bugs.freedesktop.org/show_bug.cgi?id=64257 --- Comment #49 from vincent v...@ovi.com --- Created attachment 80739 -- https://bugs.freedesktop.org/attachment.cgi?id=80739action=edit Force max tex size of 8 Does this patch help ? I assumed a max tex clause size of 16 for anything from

[Bug 64257] RS880 issues with r600-llvm-compiler

https://bugs.freedesktop.org/show_bug.cgi?id=64257 --- Comment #50 from Alex Deucher ag...@yahoo.com --- 6xx has a max tex/vtx clause size of 8. 7xx+ has a max tex/vtx clause size of 16. In CF_WORD1, make sure you are setting the MSB of the count field. Bits 12:10 and bit 19 make up the total

[Bug 65416] r300g does not eliminate unread varyings

https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #5 from Marek Olšák mar...@gmail.com --- I have implemented it, but there is a problem. If I enable the optimization, EXT_separate_shader_objects must be disabled. Is it okay with you? This is a valid sequence with EXT_sso:

[Bug 64257] RS880 issues with r600-llvm-compiler

https://bugs.freedesktop.org/show_bug.cgi?id=64257 vincent v...@ovi.com changed: What|Removed |Added Attachment #80739|0 |1 is obsolete|

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 1:05 PM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux

[Bug 64257] RS880 issues with r600-llvm-compiler

https://bugs.freedesktop.org/show_bug.cgi?id=64257 --- Comment #52 from Andy Furniss adf.li...@gmail.com --- (In reply to comment #51) Created attachment 80740 [details] [review] Properly set COUNT_3 Indeed, I was always setting COUNT_3 to 0. This new patch should solve the issue (at

Re: [PATCH] drm/mgag200: Don't do full cleanup if mgag200_device_init fails

Dear Christopher, Am Mittwoch, den 05.06.2013, 11:29 -0400 schrieb Christopher Harvey: Running mgag200_driver_unload when the driver init fails early on causes functions like drm_mode_config_cleanup to be called. The problem is, drm_mode_config_cleanup crashes because the corresponding init

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 7:00 PM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: And here's another one - look carefully at this path: buf = dev-driver-gem_prime_export(dev, obj, flags); if (IS_ERR(buf)) { /* normally the created

[Bug 64257] RS880 issues with r600-llvm-compiler

https://bugs.freedesktop.org/show_bug.cgi?id=64257 vincent v...@ovi.com changed: What|Removed |Added Attachment #80740|0 |1 is obsolete|

Re: [RFC 0/2] exynos5250/hdmi: replace dummy hdmiphy clock with pmu reg control

Mr. Dae, Thanks for your valuable inputs. I posted it as RFC because, I also have received comments to register hdmiphy as a clock controller. As we always configure it for specific frequency, hdmi-phy looks similar to a PLL. But it really doesn't belong to that class. Secondly prior to

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Tue, Jun 11, 2013 at 09:48:57AM +1000, Dave Airlie wrote: On Tue, Jun 11, 2013 at 9:36 AM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Tue, Jun 11, 2013 at 09:24:16AM +1000, Dave Airlie wrote: I'd like to see all the ARM based drivers based on CMA if it can meet their

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: And having thought about this driver, DRM some more, I'm now of the opinion that DRM is not suitable for driving hardware where the GPU is an

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: And having thought about this driver, DRM some more, I'm now of the

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 06:05:12PM +0100, Russell King - ARM Linux wrote: On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux li...@arm.linux.org.uk

Re: [PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

And here's another one - look carefully at this path: buf = dev-driver-gem_prime_export(dev, obj, flags); if (IS_ERR(buf)) { /* normally the created dma-buf takes ownership of the ref, * but if that fails then drop

[PATCH] drm/nouveau: perform a bar flush when flushing vm

On Tue, Jun 11, 2013 at 10:17 PM, Maarten Lankhorst wrote: > Appears to fix the regression from "drm/nvc0/vm: handle bar tlb flushes > internally". > nvidia always seems to do this flush after writing values. Thanks, patch applied. > > Signed-off-by: Maarten Lankhorst > --- > diff --git

[PATCH v4] drm/exynos: hdmi: use drm_display_mode to check the supported modes

> -static int mixer_check_timing(void *ctx, struct fb_videomode *timing) > +static int mixer_check_mode(void *ctx, struct drm_display_mode *mode) > { > u32 w, h; > > - w = timing->xres; > - h = timing->yres; > + w = mode->hdisplay; > + h = mode->vdisplay; > > - DRM_DEBUG_KMS("%s : xres=%d, yres=%d, refresh=%d, intl=%d\n", > - __func__, timing->xres, timing->yres, > - timing->refresh, (timing->vmode & > - FB_VMODE_INTERLACED) ? true : false); > + DRM_DEBUG_KMS("xres=%d, yres=%d, refresh=%d, intl=%d\n", > + mode->hdisplay, mode->vdisplay, mode->vrefresh, > + (mode->flags & DRM_MODE_FLAG_INTERLACE) ? 1 : 0); > > if ((w >= 464 && w <= 720 && h >= 261 && h <= 576) || > (w >= 1024 && w <= 1280 && h >= 576 && h <= 720) || > @@ -978,7 +977,7 @@ static struct exynos_mixer_ops mixer_ops = { > .win_disable= mixer_win_disable, > > /* display */ > - .check_timing = mixer_check_timing, > + .check_mode = mixer_check_mode, > }; > > static irqreturn_t mixer_irq_handler(int irq, void *arg) > -- > 1.7.10.4 > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-samsung-soc" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/ed8969ee/attachment-0001.html>

[RFC 0/2] exynos5250/hdmi: replace dummy hdmiphy clock with pmu reg control

re majordomo info at http://vger.kernel.org/majordomo-info.html > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/e2130c01/attachment.html>

[RFC 0/2] exynos5250/hdmi: replace dummy hdmiphy clock with pmu reg control

amsung-soc" in >> the body of a message to majordomo at vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/b557afea/attachment.html>

[PATCH] drm: encoder_slave: respect of_node on i2c encoder init

On 06/11/2013 05:10 PM, Francisco Jerez wrote: > Sebastian Hesselbarth writes: >>> - I think we could also drop the call to ->set_config since presumably an >>> of-enabled driver grabbed any required info already from the dt. >> [...] >>> I think this way we could still share encoder slaves

[PATCH 9/9] ARM/dts: update device tree binding documentation for hdmi susbsystem

On Tue, 11 Jun 2013 19:41:31 +0530, Rahul Sharma wrote: > Update device tree binding documentation for hdmi subsystem with the > clock information, phy property information and compatible strings for > exynos5420. > > Signed-off-by: Rahul Sharma Binding looks reasonable to me. I'll leave it

[Bug 24066] On the Rain-Slick Precipice of Darkness, Episode One crashes before first starting screen

64, ATI 4850x2 Agra -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/6de130fb/attachment.html>

[RFC 1/21] Add VIA DRM driver

> commit 1fcf23d361375645d586756d126b436796ba4fba > Author: James Simmons > Date: Sat Jun 8 09:31:57 2013 -0400 > > via: New KMS ioctls and hardware to support. > > Add new VIA pci ids to support newer hardware. Cleanup userspace > api structs to remove kernel types and add the new

[git pull] drm fixes

Hi Linus, just some GMA500 memory leaks and i915 regression fix due to regression fix. Dave. The following changes since commit ab0296319a8cb970f4e42659472bb40fbfae3e56: Merge tag 'spi-v3.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (2013-06-10 13:28:39 -0700)

[PATCH v4 0/4] add mutex wait/wound/style style locks

Op 28-05-13 16:48, Maarten Lankhorst schreef: > Version 4 already? > > Small api changes since v3: > - Remove ww_mutex_unlock_single and ww_mutex_lock_single. > - Rename ww_mutex_trylock_single to ww_mutex_trylock. > - Remove separate implementations of ww_mutex_lock_slow*, normal > functions

[PATCH] drm: Don't pass negative delta to ktime_sub_ns()

From: Michel D?nzer It takes an unsigned value. This happens not to blow up on 64-bit architectures, but it does on 32-bit, causing drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus timestamps for vblank events. Which in turn causes e.g. gnome-shell to

[PATCH] radeon: Fix a false positive lockup after 10s of inactivity

On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: > If the device is idle for over ten seconds, then the next attempt to do > anything can race with the lockup detector and cause a bogus lockup > to be detected. > > Oddly, the situation is well-described in the lockup detector's comments

[PATCH 2/6] gpu: host1x: Fix syncpoint wait return value

On 11.06.2013 15:09, Daniel Vetter wrote: > Maybe it wasn't clear, but -EAGAIN does _not_ resubmit work. -EAGAIN > is used to restart the ioctl if we had to kick a thread (to make sure > it doesn't hold any locks), e.g. for a blocking wait on oustanding > rendering. The codepaths taken work

[PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, Jun 12, 2013 at 11:58:44AM +0200, Michel D?nzer wrote: > From: Michel D?nzer > > It takes an unsigned value. This happens not to blow up on 64-bit > architectures, but it does on 32-bit, causing > drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus > timestamps for vblank

[PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, 2013-06-12 at 11:58 +0200, Michel D?nzer wrote: > From: Michel D?nzer > > It takes an unsigned value. This happens not to blow up on 64-bit > architectures, but it does on 32-bit, causing > drm_calc_vbltimestamp_from_scanoutpos() to calculate totally bogus > timestamps for vblank events.

[PATCH 2/6] gpu: host1x: Fix syncpoint wait return value

On Wed, Jun 12, 2013 at 12:28 PM, Terje Bergstr?m wrote: > On 11.06.2013 15:09, Daniel Vetter wrote: >> Maybe it wasn't clear, but -EAGAIN does _not_ resubmit work. -EAGAIN >> is used to restart the ioctl if we had to kick a thread (to make sure >> it doesn't hold any locks), e.g. for a blocking

[PATCH] drm: Don't pass negative delta to ktime_sub_ns()

On Wed, Jun 12, 2013 at 11:48:13AM +0100, Chris Wilson wrote: > On Wed, Jun 12, 2013 at 11:58:44AM +0200, Michel D?nzer wrote: > > From: Michel D?nzer > > > > It takes an unsigned value. This happens not to blow up on 64-bit > > architectures, but it does on 32-bit, causing > >

[PATCH] radeon: Fix a false positive lockup after 10s of inactivity

Am 12.06.2013 12:26, schrieb Michel D?nzer: > On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: >> If the device is idle for over ten seconds, then the next attempt to do >> anything can race with the lockup detector and cause a bogus lockup >> to be detected. >> >> Oddly, the situation is

[PATCH 0/3] drm/cma: use prim helpers instead GEM CMA specific dma_buf functionality

Hi, GEM CMA supports dma_buf but it needs GEM CMA specific functionality for dma_buf. We can use prime helpers for dma_buf by commit 89177644a7b6306e6084a89eab7e290f4bfef397 "drm: add prime helpers", so this patchset is to replace from using GEM CMA specific functions to using prime helpers.

[PATCH 1/3] drm: add mmap function to prime helpers

This adds to call low-level mmap() from prime helpers. Signed-off-by: Joonyoung Shim --- drivers/gpu/drm/drm_prime.c | 5 - include/drm/drmP.h | 2 ++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index

[PATCH 2/3] drm/cma: add low-level hook functions to use prime helpers

Instead of using the dma_buf functionality for GEM CMA, we can use prime helpers if we can provide low-level hook functions for GEM CMA. Signed-off-by: Joonyoung Shim --- drivers/gpu/drm/drm_gem_cma_helper.c | 76 include/drm/drm_gem_cma_helper.h | 9

[PATCH 3/3] drm/cma: remove GEM CMA specific dma_buf functionality

We can use prime helpers instead. Signed-off-by: Joonyoung Shim --- drivers/gpu/drm/drm_gem_cma_helper.c | 283 --- include/drm/drm_gem_cma_helper.h | 6 - 2 files changed, 289 deletions(-) diff --git a/drivers/gpu/drm/drm_gem_cma_helper.c

[PATCH 0/3] drm/cma: use prim helpers instead GEM CMA specific dma_buf functionality

Hi Joonyoung, Thank you for the patches. I'll try to review and test them next week. On Wednesday 12 June 2013 22:16:14 Joonyoung Shim wrote: > Hi, > > GEM CMA supports dma_buf but it needs GEM CMA specific functionality for > dma_buf. We can use prime helpers for dma_buf by commit >

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux wrote: > On Tue, Jun 11, 2013 at 09:48:57AM +1000, Dave Airlie wrote: >> On Tue, Jun 11, 2013 at 9:36 AM, Russell King - ARM Linux >> wrote: >> > On Tue, Jun 11, 2013 at 09:24:16AM +1000, Dave Airlie wrote: >> >> I'd like to see all the

[PATCH] radeon: Fix a false positive lockup after 10s of inactivity

On Wed, Jun 12, 2013 at 6:26 AM, Michel D?nzer wrote: > On Die, 2013-06-11 at 16:23 -0700, Andy Lutomirski wrote: >> If the device is idle for over ten seconds, then the next attempt to do >> anything can race with the lockup detector and cause a bogus lockup >> to be detected. >> >> Oddly, the

[PATCH] drm/mgag200: Don't do full cleanup if mgag200_device_init fails

On Wed, Jun 05 2013, Christopher Harvey wrote: > Running mgag200_driver_unload when the driver init fails early on > causes functions like drm_mode_config_cleanup to be called. The > problem is, drm_mode_config_cleanup crashes because the corresponding > init hasn't happend yet. There really

[PATCH] drm/mgag200: Hardware cursor support

On Wed, Jun 05 2013, Christopher Harvey wrote: > G200 cards support, at best, 16 colour palleted images for the cursor > so we do a conversion in the cursor_set function, and reject cursors > with more than 16 colours, or cursors with partial transparency. Xorg > falls back gracefully to software

[PATCH 1/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

This code was ported from the old xorg mga driver. These limits were implemented as a solution to a number of problems that were seen. These problems were linked to the bandwidth limitations of the g200e series. Signed-off-by: Julia Lemire --- drivers/gpu/drm/mgag200/mgag200_drv.h | 41

[PATCH 0/1] drm/mgag200: Added resolution and bandwidth limits for various G200e products.

At the larger resolutions, the g200e series sometimes struggles with maintaining a proper output. Problems like flickering or black bands appearing on screen can occur. In order to avoid this, limitations regarding resolutions and bandwidth have been added for the different variations of the

[Bug 64257] RS880 issues with r600-llvm-compiler

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/a7470984/attachment.html>

[Bug 64257] RS880 issues with r600-llvm-compiler

suspect you are not setting bit 19 properly. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/146edd9c/attachment.html>

[Bug 65416] r300g does not eliminate unread varyings

because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/fce722e5/attachment.html>

[Bug 64257] RS880 issues with r600-llvm-compiler

URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/0bfff57e/attachment.html>

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 1:05 PM, Russell King - ARM Linux wrote: > On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: >> On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: >> > On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux >> > wrote: >> > > And having

[Bug 64257] RS880 issues with r600-llvm-compiler

max tex size of 8 does fix it. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130612/9cf48340/attachment.html>

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 7:00 PM, Russell King - ARM Linux wrote: > And here's another one - look carefully at this path: > > buf = dev->driver->gem_prime_export(dev, obj, flags); > if (IS_ERR(buf)) { > /* normally the created dma-buf takes

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Tue, Jun 11, 2013 at 09:48:57AM +1000, Dave Airlie wrote: > On Tue, Jun 11, 2013 at 9:36 AM, Russell King - ARM Linux > wrote: > > On Tue, Jun 11, 2013 at 09:24:16AM +1000, Dave Airlie wrote: > >> I'd like to see all the ARM based drivers based on CMA if it can meet > >> their requirements >

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: > On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux > wrote: > > And having thought about this driver, DRM some more, I'm now of the > > opinion that DRM is not suitable for driving hardware where the GPU is > > an entirely

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: > On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: > > On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux > > wrote: > > > And having thought about this driver, DRM some more, I'm now of the > > > opinion

[PATCH RFC 2/8] DRM: Armada: Add Armada DRM driver

On Wed, Jun 12, 2013 at 06:05:12PM +0100, Russell King - ARM Linux wrote: > On Wed, Jun 12, 2013 at 05:49:14PM +0100, Russell King - ARM Linux wrote: > > On Wed, Jun 12, 2013 at 09:56:22AM -0400, Rob Clark wrote: > > > On Wed, Jun 12, 2013 at 9:48 AM, Russell King - ARM Linux > > > wrote: > > > >