[PATCH] drm/dsi: Do the 'msg' check prior to dereferencing it.

From: Fabio Estevam Commit a52879e8d7cb ("drm/dsi: Add message to packet translator") caused the following Smatch complaint: drivers/gpu/drm/drm_mipi_dsi.c:328 mipi_dsi_create_packet() warn: variable dereferenced before check 'msg' (see line 326) Do the

[PATCH 3/8] drm/irq: Add drm_crtc_vblank_count()

On Tue, Dec 16, 2014 at 05:15:10PM +0100, Thierry Reding wrote: > From: Thierry Reding > > This function is the KMS native variant of drm_vblank_count(). It takes > a struct drm_crtc * instead of a struct drm_device * and an index of the > CRTC. > > Eventually the goal is to access vblank data

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #11 from Bernd Steinhauser --- Hm, ok. So should I still try the steps above? Because trying to use drm_radeon as a module would require me to do some testing with that setup before. (In reply to Oded Gabbay from comment #8) > 2.

[PATCH v2] drm/exynos/fimd: only finish pageflip if START == START_S

On 2014년 12월 11일 01:57, Gustavo Padovan wrote: > From: Daniel Kurtz > > A framebuffer gets committed to FIMD's default window like this: > exynos_drm_crtc_update() > exynos_plane_commit() >fimd_win_commit() > > fimd_win_commit() programs BUF_START[0]. At each vblank, FIMD hardware

[PATCH] drm: Move ->get_scanout_position() to struct drm_crtc_funcs

On Tue, Dec 16, 2014 at 06:00:14PM +0100, Thierry Reding wrote: > From: Thierry Reding > > None of the drivers use this in legacy mode, so it can be converted to > use struct drm_crtc * directly. While at it, also make the sole user of > the callback, drm_calc_vbltimestamp_from_scanoutpos(),

[PATCH 11/13] drm/irq: Document return values more consistently

On Tue, Dec 16, 2014 at 05:53:33PM +0100, Thierry Reding wrote: > From: Thierry Reding > > Some of the functions are documented inconsistently. Add Returns: > sections where missing and use consistent style to describe the return > value. > > Signed-off-by: Thierry Reding With the comment in

[PATCH 12/13] drm/irq: Expel legacy API

On Tue, Dec 16, 2014 at 06:59:28PM +0100, Daniel Vetter wrote: > On Tue, Dec 16, 2014 at 05:53:34PM +0100, Thierry Reding wrote: > > From: Thierry Reding > > > > These legacy functions all operate on the struct drm_device * and an > > index to the CRTC that they should access. This is bad

[PATCH 12/13] drm/irq: Expel legacy API

On Tue, Dec 16, 2014 at 05:53:34PM +0100, Thierry Reding wrote: > From: Thierry Reding > > These legacy functions all operate on the struct drm_device * and an > index to the CRTC that they should access. This is bad because it > requires keeping track of a global data structures to resolve the

[PATCH 09/13] drm/irq: Make pipe unsigned and name consistent

On Tue, Dec 16, 2014 at 05:53:31PM +0100, Thierry Reding wrote: > -void drm_wait_one_vblank(struct drm_device *dev, int crtc) > +void drm_wait_one_vblank(struct drm_device *dev, unsigned int pipe) > { > + struct drm_vblank_crtc *vblank = >vblank[pipe]; > int ret; > u32 last; > >

[PATCH] drm/info: Remove unused code

On Tue, Dec 16, 2014 at 12:02:13PM +0100, Thierry Reding wrote: > From: Thierry Reding > > Commit 28a62277e06f ("drm: Convert proc files to seq_file and introduce > debugfs") converted /proc files to debugfs and in the process dropped > the entry for the vblank statistics. Since that file has

[PATCH 05/13] drm/imx: Store correct CRTC index in events

Am Dienstag, den 16.12.2014, 17:53 +0100 schrieb Thierry Reding: > From: Thierry Reding > > A negative pipe causes a special case to be triggered for drivers that > don't have proper VBLANK support. i.MX does support VBLANKs, so there is > no need for the fallback code. > > Cc: Philipp Zabel >

[PATCH 04/13] drm/imx: Make pipe number unsigned

Am Dienstag, den 16.12.2014, 17:53 +0100 schrieb Thierry Reding: > From: Thierry Reding > > There's no reason whatsoever why this should ever be negative. > > Cc: Philipp Zabel > Signed-off-by: Thierry Reding Acked-by: Philipp Zabel thanks Philipp

[PATCH 13/13] RFC: drm: Atomic modeset ioctl

The atomic modeset ioctl can be used to push any number of new values for object properties. The driver can then check the full device configuration as single unit, and try to apply the changes atomically. The ioctl simply takes a list of object IDs and property IDs and their values. Originally

[PATCH 12/13] drm/msm: atomic property support

Not too much to do, as we haven't exposed any driver custom properties yet, so all we need to do is plug in the helpers. Signed-off-by: Rob Clark --- drivers/gpu/drm/msm/hdmi/hdmi_connector.c | 1 + drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c | 1 +

[PATCH 11/13] drm/atomic: atomic connector properties

Expose the core connector state as properties so it can be updated via atomic ioctl. Signed-off-by: Rob Clark --- Documentation/DocBook/drm.tmpl | 11 +-- drivers/gpu/drm/drm_atomic.c | 9 +++-- drivers/gpu/drm/drm_crtc.c | 13 + 3 files changed, 25 insertions(+),

[PATCH 10/13] drm/atomic: atomic plane properties

Expose the core plane state as properties, so they can be updated via atomic ioctl. Signed-off-by: Rob Clark --- Documentation/DocBook/drm.tmpl | 74 -- drivers/gpu/drm/drm_atomic.c | 69 --- drivers/gpu/drm/drm_crtc.c |

[PATCH 09/13] drm/atomic: atomic_check functions

Add functions to check core plane/crtc state. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_atomic.c| 87 + drivers/gpu/drm/drm_atomic_helper.c | 47 ++-- include/drm/drm_atomic.h| 4 ++ 3 files changed, 124

[PATCH 08/13] drm: tweak getconnector locking

We need to hold connection_mutex as we read the properties. Easiest thing is just widen the scope where connection_mutex is held. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_crtc.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc.c

[PATCH 07/13] drm: small property creation cleanup

Getting ready to add a lot more standard properties for atomic. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_crtc.c | 27 +-- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c index

[PATCH 06/13] drm: add atomic hook to read property plus helper

Once a driver is using atomic helpers for modeset, the next step is to switch over to atomic properties. To do this, plug in the helper function to your modeconfig funcs and be sure to implement the plane/ crtc/connector atomic_{get,set}_property vfuncs for any of your mode- objects which have

[PATCH 05/13] drm: add atomic_get_property

Since we won't be using the obj->properties->values[] array to shadow property values for atomic drivers, we are going to need a vfunc for getting prop values. Add that along w/ mandatory wrapper fxns. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_atomic.c | 76

[PATCH 04/13] drm: add atomic_set_property wrappers

As we add properties for all the standard plane/crtc/connector attributes (in preperation for the atomic ioctl), we are going to want to handle core state in core (rather than per driver). Intercepting the core properties will be easier if the atomic_set_property vfuncs are not called directly,

[PATCH 03/13] drm: get rid of direct property value access

For atomic drivers, we won't use the values array but instead shunt things off to obj->atomic_get_property(). So to simplify things make all read/write of properties values go through the accessors. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_crtc.c | 19 +++

[PATCH 02/13] drm: store property instead of id in obj attachment

Keep property pointer, instead of id, in per mode-object attachments. This will simplify things in later patches. Signed-off-by: Rob Clark --- drivers/gpu/drm/drm_crtc.c | 17 - include/drm/drm_crtc.h | 7 ++- 2 files changed, 14 insertions(+), 10 deletions(-) diff

[PATCH 01/13] drm: allow property validation for refcnted props

We can already have object properties, which technically can be fb's. Switch the property validation logic over to a get/put style interface so it can take a ref to refcnt'd objects, and then drop that ref after the driver has a chance to take it's own ref. Signed-off-by: Rob Clark ---

[PATCH 00/13] Atomic Properties

Now that we have core atomic helpers, let's expose that to userspace! The first step here is to, for drivers supporting atomic, expose all the core plane/CRTC/connector state as properties. Once this is in place, all that remains is the atomic ioctl to allow userspace to atomically set a bunch of

[PATCH] drm: Move ->get_scanout_position() to struct drm_crtc_funcs

From: Thierry Reding None of the drivers use this in legacy mode, so it can be converted to use struct drm_crtc * directly. While at it, also make the sole user of the callback, drm_calc_vbltimestamp_from_scanoutpos(), pass through the CRTC directly. Cc: Daniel Vetter Cc:

[PATCH 13/13] drm/irq: Move some prototypes to drm_crtc.h

From: Thierry Reding The new prototypes that deal with struct drm_crtc * directly are better located in include/drm/drm_crtc.h along with the other functions that deal with CRTCs. Signed-off-by: Thierry Reding --- include/drm/drmP.h | 17 -

[PATCH 12/13] drm/irq: Expel legacy API

From: Thierry Reding These legacy functions all operate on the struct drm_device * and an index to the CRTC that they should access. This is bad because it requires keeping track of a global data structures to resolve the index to CRTC object lookup. In order to get rid of

[PATCH 11/13] drm/irq: Document return values more consistently

From: Thierry Reding Some of the functions are documented inconsistently. Add Returns: sections where missing and use consistent style to describe the return value. Signed-off-by: Thierry Reding --- drivers/gpu/drm/drm_irq.c | 7 +-- 1 file changed, 5 insertions(+), 2

[PATCH 10/13] drm/irq: Add drm_crtc_vblank_count_and_time()

From: Thierry Reding This function is the KMS native variant of drm_vblank_count_and_time(). It takes a struct drm_crtc * instead of a struct drm_device * and an index of the CRTC. Eventually the goal is to access vblank data through the CRTC only so that the per-CRTC data

[PATCH 09/13] drm/irq: Make pipe unsigned and name consistent

From: Thierry Reding Name all references to the pipe number (CRTC index) consistently to make it easier to distinguish which is a pipe number and which is a pointer to struct drm_crtc. While at it also make all references to the pipe number unsigned because there is no

[PATCH 08/13] drm/irq: Check for valid VBLANK before dereference

From: Thierry Reding When accessing the array of per-CRTC VBLANK structures we must always check that the index into the array is valid before dereferencing to avoid crashing. Signed-off-by: Thierry Reding --- drivers/gpu/drm/drm_irq.c | 7 +-- 1 file changed, 5

[PATCH 07/13] drm/sti: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. STi does support VBLANKs, so there is no need for the fallback code. Cc: Benjamin Gaignard Signed-off-by: Thierry Reding ---

[PATCH 06/13] drm/rockchip: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. Rockchip does support VBLANKs, so there is no need for the fallback code. Cc: Mark Yao Signed-off-by: Thierry Reding ---

[PATCH 05/13] drm/imx: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. i.MX does support VBLANKs, so there is no need for the fallback code. Cc: Philipp Zabel Signed-off-by: Thierry Reding ---

[PATCH 04/13] drm/imx: Make pipe number unsigned

From: Thierry Reding There's no reason whatsoever why this should ever be negative. Cc: Philipp Zabel Signed-off-by: Thierry Reding --- drivers/gpu/drm/imx/imx-drm-core.c | 4 ++-- drivers/gpu/drm/imx/imx-drm.h | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)

[PATCH 03/13] drm/exynos: Store correct CRTC index in events

From: Thierry Reding A negative pipe causes a special case to be triggered for drivers that don't have proper VBLANK support. Exynos does support VBLANKs, so there is no need for the fallback code. Cc: Inki Dae Cc: Joonyoung Shim Cc: Seung-Woo Kim Cc: Kyungmin Park

[PATCH 02/13] drm/bochs: Store correct CRTC index in events

From: Thierry Reding Previously a negative pipe caused a special case to be triggered for drivers that didn't have proper VBLANK support. The trigger for this special case is now independent of the pipe, so the correct CRTC index can now be stored in events. Cc: Gerd

[PATCH 01/13] drm/irq: Remove negative CRTC index special-case

From: Thierry Reding The drm_send_vblank_event() function treats negative CRTC indices as meaning that a driver doesn't have proper VBLANK handling. This is the only place where DRM needs negative CRTC indices, so in order to enable subsequent cleanup, remove this special

[PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio

在 2014年12月16日 17:34, Russell King - ARM Linux 写道: > On Tue, Dec 16, 2014 at 02:17:51PM +0800, Kuankuan.Yang wrote: >> hdmi-audio driver share irq with dw_hdmi driver, for continuing AHBAUDDMA >> or for detecting hdmi insert. >> So maybe it's hard to switch to simple-card way,

[Bug 85421] radeon stalled, GPU lockup, reset and failed on resume; crashed by firefox.

https://bugzilla.kernel.org/show_bug.cgi?id=85421 --- Comment #20 from Hin-Tak Leung --- mesa 10.4.0 also crashed on me (fedora provides it so I thought I'll let my 10.2.9 upgrade to have a go), on the first day. first there are some errors in dmesg (running mplayer , not as much as under

[PATCH 8/8] drm/tegra: gem: Use the proper size for GEM objects

From: Thierry Reding If the requested buffer size wasn't a multiple of the page size, the IOMMU code would round down the size to the next multiple of the page size, thereby causing translation errors. To fix this we no longer pass around the requested size but reuse the

[PATCH 7/8] drm/tegra: gem: Flush buffer objects upon allocation

From: Thierry Reding Buffers obtained via shmem may still have associated cachelines. If they aren't properly flushed they may cause framebuffer corruption if the cache gets flushed after the application has drawn to it. Signed-off-by: Thierry Reding ---

[PATCH 6/8] drm/cache: Implement drm_clflush_*() for ARM

From: Thierry Reding Add implementations for drm_clflush_*() on ARM by borrowing code from the DMA mapping API implementation. Unfortunately ARM doesn't export an API to flush caches on a page by page basis, so this replicates most of the code. Reviewed--by: Rob Clark

[PATCH 5/8] drm/tegra: dc: Fix a potential race on page-flip completion

From: Thierry Reding Page-flip completion could race with page-flip submission, so extend the critical section to include all accesses to page-flip related data. Reported-by: Alexandre Courbot Signed-off-by: Thierry Reding --- drivers/gpu/drm/tegra/dc.c | 10 +++--- 1

[PATCH 4/8] drm/tegra: dc: Consistently use the same pipe

From: Thierry Reding The hardware pipe numbers don't always match the DRM CRTC indices. This can happen for example if the first display controller defers probe, causing it to be registered with DRM after the second display controller. When that happens the hardware pipe

[PATCH 3/8] drm/irq: Add drm_crtc_vblank_count()

From: Thierry Reding This function is the KMS native variant of drm_vblank_count(). It takes a struct drm_crtc * instead of a struct drm_device * and an index of the CRTC. Eventually the goal is to access vblank data through the CRTC only so that the per-CRTC data can be

[PATCH 2/8] drm/irq: Add drm_crtc_handle_vblank()

From: Thierry Reding This function is the KMS native variant of drm_handle_vblank(). It takes a struct drm_crtc * instead of a struct drm_device * and an index of the CRTC. Eventually the goal is to access vblank data through the CRTC only so that the per-CRTC data can be

[PATCH 1/8] drm/irq: Add drm_crtc_send_vblank_event()

From: Thierry Reding This function is the KMS native variant of drm_send_vblank_event(). It takes a struct drm_crtc * instead of a struct drm_device * and an index of the CRTC. Eventually the goal is to access vblank data through the CRTC only so that the per-CRTC data can

[PATCH 0/8] drm/tegra: Fixes for v3.19-rc1

From: Thierry Reding Hi, This is a set of fixes for two regressions and one bug in the IOMMU mapping code. It turns out that all of these issues turn up primarily on Tegra30 hardware. The IOMMU mapping bug only manifests on buffers that aren't multiples of the page size. I

Long radeon stalls on recent kernels

On 11.12.2014 14:13, Andy Lutomirski wrote: > On Wed, Dec 10, 2014 at 8:24 PM, Michel Dänzer wrote: >> On 11.12.2014 05:28, Andy Lutomirski wrote: >>> On Wed, Dec 10, 2014 at 1:44 AM, Michel Dänzer >>> wrote: On 10.12.2014 06:39, Andy Lutomirski wrote: > On Tue, Dec 9, 2014 at 8:06

[RFC] drm: add support for tiled/compressed/etc modifier in addfb2

On Mon, Dec 15, 2014 at 10:19:47PM +, Daniel Stone wrote: > Hi, > > On 12 December 2014 at 18:22, Ville Syrjälä linux.intel.com> > wrote: > > > > On Fri, Dec 12, 2014 at 06:05:49PM +, Daniel Stone wrote: > > > On 12 December 2014 at 18:00, Ville Syrjälä < > > ville.syrjala at

[PATCH] nouveau: bring back legacy mmap handler

From: Dave Airlie nouveau userspace back at 1.0.1 used to call the X server DRIOpenDRMMaster interface even for DRI2 (doh!), this attempts to map the sarea and fails if it can't. Since 884c6dabb0eafe7227f099c9e78e514191efaf13 from Daniel, this fails, but only ancient drivers

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #10 from Oded Gabbay --- Hi, So I managed to recreate the bug on my setup. This is happening because you compiled all the modules inside the kernel. I need to address that, but for now, if you will compile them as "m", everything is

drm: rockchip: Add basic drm driver

Hello Mark Yao, The patch 2048e3286f34: "drm: rockchip: Add basic drm driver" from Aug 22, 2014, leads to the following static checker warning: drivers/gpu/drm/rockchip/rockchip_drm_vop.c:1383 vop_bind() warn: unsigned 'vop->irq' is never less than zero.

[PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio

在 2014年12月16日 00:18, Mark Brown 写道: > On Mon, Dec 15, 2014 at 09:10:26PM +0800, Kuankuan.Yang wrote: >> Hi Mark & Russell: > Please don't top post, that way people have some context for what you're > saying - look at how people normally format their mails on thelist. > >> In that way,

[PATCH] drm: sti: add DVO output connector

Digital Video Out connector driver LCD panels. Like HDMI and HDA it create bridge, encoder and connector drm object. Add binding descrition. Signed-off-by: Benjamin Gaignard --- .../devicetree/bindings/gpu/st,stih4xx.txt | 29 ++ drivers/gpu/drm/sti/Makefile | 4

[PATCH 0/8] drm/tegra: Fixes for v3.19-rc1

On Tue, Dec 16, 2014 at 11:15 AM, Thierry Reding wrote: > From: Thierry Reding > > Hi, > > This is a set of fixes for two regressions and one bug in the IOMMU > mapping code. It turns out that all of these issues turn up primarily > on Tegra30 hardware. The IOMMU mapping bug only manifests on

[RFC] drm: add support for tiled/compressed/etc modifier in addfb2

On 12.12.2014 20:27, Daniel Stone wrote: > On 10 December 2014 at 17:17, Rob Clark > wrote: > > In DRM/KMS we are lacking a good way to deal with tiled/compressed > formats. Especially in the case of dmabuf/prime buffer sharing, where > we cannot

[git pull] drm for 3.19-rc1

> Having a quiet deprecation warning with the understanding that things > will stay around for *years* is fine. Although it makes me wonder how > much value the deprecation message really adds. I mean, why the hell > print a message, when the only correct thing to do is to just look at > and fix

[PATCH] drm/info: Remove unused code

From: Thierry Reding Commit 28a62277e06f ("drm: Convert proc files to seq_file and introduce debugfs") converted /proc files to debugfs and in the process dropped the entry for the vblank statistics. Since that file has been gone for almost five years, there is no use to keep

[git pull] drm for 3.19-rc1

On 16 December 2014 at 11:03, Linus Torvalds wrote: > On Mon, Dec 15, 2014 at 4:48 PM, Dave Airlie wrote: >> >> I'd be inclined to just revert this for now, it is annoying we let >> userspace away with this, but we probably need to find a better >> way to enforce it, since the cat is out of the

[Intel-gfx] [PATCH 4/4] drm/i915: Opportunistically reduce flushing at execbuf

On Tue, Dec 16, 2014 at 07:57:39AM +, Chris Wilson wrote: > On Mon, Dec 15, 2014 at 01:06:40PM -0800, Ben Widawsky wrote: > > On Mon, Dec 15, 2014 at 08:39:35PM +, Chris Wilson wrote: > > > On Mon, Dec 15, 2014 at 11:56:05AM -0800, Ben Widawsky wrote: > > > > On Mon, Dec 15, 2014 at

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #9 from Oded Gabbay --- One more thing, I'm trying to understand the exact tree you are using so we will look at the same code. Did you just took drm-next, or did you manually merged between trees ? If you did a manual merge, could

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #8 from Oded Gabbay --- Hi, Three things, please: 1. Please try the attached patch. It tries to verify more pointers before using them. 2. You said CONFIG_HSA_AMD=y. What's the value of CONFIG_DRM_RADEON ? If its "m", could you

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #7 from Oded Gabbay --- Created attachment 160751 --> https://bugzilla.kernel.org/attachment.cgi?id=160751=edit More checks on pointers being used -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 89661] Kernel panic when trying use amdkfd driver on Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=89661 --- Comment #6 from Bernd Steinhauser --- Tried the patch, exactly the same result. -- You are receiving this mail because: You are watching the assignee of the bug.

[git pull] drm for 3.19-rc1

On 16 December 2014 at 10:35, Linus Torvalds wrote: > On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote: >> >> i915: >> Initial Skylake (SKL) support >> gen3/4 reset work >> start of dri1/ums removal >> infoframe tracking >> fixes for lots of things. > >

[PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio

在 2014年12月16日 00:18, Mark Brown 写道: > On Mon, Dec 15, 2014 at 09:10:26PM +0800, Kuankuan.Yang wrote: >> Hi Mark & Russell: > Please don't top post, that way people have some context for what you're > saying - look at how people normally format their mails on thelist. got it, thanks

[PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio

Hi Mark : Got it, it will be good to use simple-card. i will try it in next version. Best Regards. 在 2014年12月16日 00:18, Mark Brown 写道: > On Mon, Dec 15, 2014 at 09:10:26PM +0800, Kuankuan.Yang wrote: >> Hi Mark & Russell: > Please don't top post, that way people have some context

[PATCH] Add new DRM_MODE_CONNECTOR and _ENCODER defines

On Tue, 16 Dec 2014, Adam Cheney wrote: > --- > This email message is for the sole use of the intended recipient(s) and may > contain > confidential information. Any unauthorized review, use, disclosure or >

[PATCH] nouveau: bring back legacy mmap handler

On Tue, Dec 16, 2014 at 04:34:39PM +1000, Dave Airlie wrote: > From: Dave Airlie > > nouveau userspace back at 1.0.1 used to call the X server > DRIOpenDRMMaster interface even for DRI2 (doh!), this attempts > to map the sarea and fails if it can't. > > Since

[PATCH] drm/i915: tame the chattermouth (v2)

On Mon, Dec 15, 2014 at 10:22:49PM +0200, Jani Nikula wrote: > On Mon, 15 Dec 2014, Rob Clark wrote: > > Many distro's have mechanism in place to collect and automatically file > > bugs for failed WARN()s. And since i915 has a lot of hw state sanity > > checks which result in WARN(), it

[PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio

On Tue, Dec 16, 2014 at 02:17:51PM +0800, Kuankuan.Yang wrote: > hdmi-audio driver share irq with dw_hdmi driver, for continuing AHBAUDDMA > or for detecting hdmi insert. > So maybe it's hard to switch to simple-card way, Russell what's your > opinion ? My "opinion" is that I need to spend some

[RFC] drm: add support for tiled/compressed/etc modifier in addfb2

On Tue, Dec 16, 2014 at 3:01 AM, Daniel Stone wrote: > Hi, > > On 16 December 2014 at 03:56, Michel Dänzer wrote: >> >> On 12.12.2014 20:27, Daniel Stone wrote: >> > It might be useful to make the interpretation modifiers bitmaskable, so >> > they can be combined (e.g. wide-range/unclamped YUV

[git pull] drm for 3.19-rc1

On Mon, Dec 15, 2014 at 04:35:29PM -0800, Linus Torvalds wrote: > On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote: > > > > i915: > > Initial Skylake (SKL) support > > gen3/4 reset work > > start of dri1/ums removal > > infoframe tracking > > fixes for

[Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games

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

[Intel-gfx] [PATCH] [v2] drm/cache: Use wbinvd helpers

On Mon, Dec 15, 2014 at 12:26:46PM -0800, Ben Widawsky wrote: > From: Ben Widawsky > > When the original drm code was written there were no centralized functions for > doing a coordinated wbinvd across all CPUs. Now (since 2010) there are, so use > them instead of rolling a new one. > > v2: On

[Bug 87265] display turned off during normal work, radeon GPU lockup

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20141216/58176bf1/attachment.html>

[Bug 87278] Packet0 not allowed and GPU fault detected errors with Serious Engine games

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20141216/1100e4b4/attachment.html>

[RFC] drm: add support for tiled/compressed/etc modifier in addfb2

4 sub-bits as a bitmask, but I don't think there's a need for combining tokens from multiple vendor spaces. Cheers, Daniel -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20141216/10f4554f/attachment.html>

[Intel-gfx] [PATCH 4/4] drm/i915: Opportunistically reduce flushing at execbuf

On Mon, Dec 15, 2014 at 01:06:40PM -0800, Ben Widawsky wrote: > On Mon, Dec 15, 2014 at 08:39:35PM +, Chris Wilson wrote: > > On Mon, Dec 15, 2014 at 11:56:05AM -0800, Ben Widawsky wrote: > > > On Mon, Dec 15, 2014 at 08:20:50AM +, Chris Wilson wrote: > > > > On Mon, Dec 15, 2014 at

[git pull] drm for 3.19-rc1

On Tue, Dec 16, 2014 at 12:37:52PM +1000, Dave Airlie wrote: > > Having a quiet deprecation warning with the understanding that things > > will stay around for *years* is fine. Although it makes me wonder how > > much value the deprecation message really adds. I mean, why the hell > > print a

[Regression] 83f45fc turns machine's screen off

On 14.12.2014, Emmanuel Benisty wrote: > >>> The following commit permanently turns my screen off when x server is > >>> started (i3 330M Ironlake): > >>> > >>> [83f45fc360c8e16a330474860ebda872d1384c8c] drm: Don't grab an fb > >>> reference for the idr > >>> > >>> Reverting this commit

[git pull] drm for 3.19-rc1

On 12/16/2014 07:18 AM, Thomas Hellstrom wrote: > On 12/16/2014 01:35 AM, Linus Torvalds wrote: >> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote: >>> i915: >>> Initial Skylake (SKL) support >>> gen3/4 reset work >>> start of dri1/ums removal >>> infoframe

[git pull] drm for 3.19-rc1

On 12/16/2014 01:35 AM, Linus Torvalds wrote: > On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote: >> i915: >> Initial Skylake (SKL) support >> gen3/4 reset work >> start of dri1/ums removal >> infoframe tracking >> fixes for lots of things. > So I'm not

[Bug 89461] [Radeon - FirePro M7740] Dual screen fails with kernel version 3.17

https://bugzilla.kernel.org/show_bug.cgi?id=89461 --- Comment #2 from Glenn Larsen --- Confirmed, the attached patch did fix the issue! Thank you! -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH V8 00/14] drm/exynos: few patches to enhance bridge chip support

Hi Javier, On Friday 12 December 2014 10:51:50 Javier Martinez Canillas wrote: > Hello, > > On 11/18/2014 07:20 AM, Ajay kumar wrote: > > On Sat, Nov 15, 2014 at 3:24 PM, Ajay Kumar wrote: > >> This series is based on master branch of Linus tree at: > >>