Re: [PATCH v2] drm/tegra: dc: Implement legacy blending

On 21.12.2017 17:03, Thierry Reding wrote: > From: Thierry Reding > > This implements alpha blending on legacy display controllers (Tegra20, > Tegra30 and Tegra114). While it's theoretically possible to support the > zpos property to enable userspace to specify the Z-order of

Re: [PATCH v2] drm/tegra: dc: Implement legacy blending

On 21.12.2017 21:46, Dmitry Osipenko wrote: > On 21.12.2017 17:03, Thierry Reding wrote: >> From: Thierry Reding >> >> This implements alpha blending on legacy display controllers (Tegra20, >> Tegra30 and Tegra114). While it's theoretically possible to support the >> zpos

[PATCH v3] Fix loading of module radeonfb on PowerMac

When the linux kernel is build with (typical kernel ship with Debian installer): CONFIG_FB_OF=y CONFIG_VT_HW_CONSOLE_BINDING=y CONFIG_FB_RADEON=m The offb driver takes precedence over module radeonfb. It is then impossible to load the module, error reported is: [ 96.551486] radeonfb

Re: [PATCH 1/2] drm/blend: Account also the primary plane of the crtc for normalized_zpos

On 21/12/17 17:12, Ville Syrjälä wrote: If the userspace knows this, then it knows which primary plane is for which crtc, right? And if it doesn't know this, then the userspace cannot associate any plane to any crtc (except what it configures itself). So... If using legacy modesetting (and

[Bug 101714] Complete System Freeze (displaycore staging 4.11)

https://bugs.freedesktop.org/show_bug.cgi?id=101714 Matt changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 101900] No HDMI HBR audio on Polaris (no TrueHD, no Atmos, no Neo:X, no HD Master audio) and static noise in sound when LPCM

https://bugs.freedesktop.org/show_bug.cgi?id=101900 --- Comment #17 from Michel Dänzer --- FWIW, according to comments on https://lwn.net/Articles/740916/: * HDMI sinks complying with the relevant specs only accept Dolby TrueHD with HDCP enabled. * There are buggy HDMI sinks

Re: [PATCH v5 01/12] dt-bindings: panel: lvds: Document power-supply property

Hi Maxime, Thank you for the patch. On Thursday, 21 December 2017 13:02:27 EET Maxime Ripard wrote: > The power-supply property is used by a vast majority of panels, including > panel-simple. Let's document it as a common property > > Reviewed-by: Rob Herring > Signed-off-by:

[Bug 102233] OpenCL segmentation fault on AMD Radeon (Kaveri+R7) with memtestCL

https://bugs.freedesktop.org/show_bug.cgi?id=102233 --- Comment #2 from Jan Vesely --- Can you try initializing the num_gpu, num_cpu, num_accel variables? clGetDeviceIDs returns CL_DEVICE_NOT_FOUND error if there are no devices matching the requested type. This does not

[PULL] drm-intel-fixes

Hi Dave, just flushing my queue of a couple of late arrivals before xmas. Pull and send on at your leisure. Happy holidays, Jani. The following changes since commit a4ffdc2b6726958c07d535318400124e3a3bc19b: drm/i915: Protect DDI port to DPLL map from theoretical race. (2017-12-19 14:59:53

[Bug 102233] OpenCL segmentation fault on AMD Radeon (Kaveri+R7) with memtestCL

https://bugs.freedesktop.org/show_bug.cgi?id=102233 --- Comment #3 from Jan Vesely --- (In reply to Senad from comment #0) > I get 100% crashes with YACMiner (crypto mining software). please report a separate bug for YACMiner -- You are receiving this mail because: You

Re: Problem rebuilding tip

Quoting Linus Walleij (2017-12-22 08:35:42) > I haven't even touched drm_syncobj.c so this conflict doesn't appear > to be mine. The conflict looks complex too. > > I guess someone else is busy fixing this up elsewhere in the world so > I just defer for a while and try rebuilding tip later. A

Re: [PATCH 1/2] drm/blend: Account also the primary plane of the crtc for normalized_zpos

On Fri, Dec 22, 2017 at 11:16:47AM +0200, Tomi Valkeinen wrote: > On 21/12/17 17:12, Ville Syrjälä wrote: > > >> If the userspace knows this, then it knows which primary plane is for > >> which crtc, right? > >> > >> And if it doesn't know this, then the userspace cannot associate any > >> plane

Re: [PATCH v5 02/12] drm/panel: lvds: Add support for the power-supply property

Hi Maxime, Thank you for the patch. On Thursday, 21 December 2017 13:02:28 EET Maxime Ripard wrote: > A significant number of panels need to power up a regulator in order to > operate properly. Add support for the power-supply property to enable and > disable such a regulator whenever needed. >

[Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)

https://bugs.freedesktop.org/show_bug.cgi?id=104082 --- Comment #1 from coolo...@gmail.com --- also getting the same issue with my vega 56, linux 4.15, mesa-git -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 104082] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)

https://bugs.freedesktop.org/show_bug.cgi?id=104082 --- Comment #2 from coolo...@gmail.com --- Created attachment 136362 --> https://bugs.freedesktop.org/attachment.cgi?id=136362=edit dmesg -- You are receiving this mail because: You are the assignee for the

[PATCH v2] drm/msm: Fix NULL deref in adreno_load_gpu

The msm/kms driver should work even if there is no GPU device specified in DT. Currently, we get a NULL dereference crash in adreno_load_gpu since the driver assumes that priv->gpu_pdev is non-NULL. Perform an additional check on priv->gpu_pdev before trying to retrieve the msm_gpu pointer from

Re: [PATCH 1/1] drm: Add dirty_rects atomic blob property for drm_plane

Thanks Ville and Daniel for for your response. I will try to come back with something later. thanks Lukasz On 21/12/2017 14:10, Daniel Vetter wrote: On Thu, Dec 21, 2017 at 02:46:55PM +0200, Ville Syrjälä wrote: > On Thu, Dec 21, 2017 at 12:10:08PM +0100, Lukasz Spintzyk wrote: > > Change-Id:

Initial release of AMD Open Source Driver for Vulkan

We are pleased to announce the initial release of AMD Open Source Driver for Vulkan. The AMD Open Source Driver for Vulkan is an open-source Vulkan driver for Radeon graphics adapters on Linux. It is built on top of AMD's Platform Abstraction Library (PAL), a shared component that is

Re: Initial release of AMD Open Source Driver for Vulkan

Hi Lothian, Thanks for testing out out driver! Officially we recommend you to stick to GCC5 for now, however, we do have a fix for the constexpr issue mentioned below that just didn’t make it to this first release. According to your diff, are you using ICC? Could you let us know the compiler

Re: [PATCH 1/2] drm/blend: Account also the primary plane of the crtc for normalized_zpos

Hi, On 2017-12-22 12:12, Ville Syrjälä wrote: > On Fri, Dec 22, 2017 at 11:16:47AM +0200, Tomi Valkeinen wrote: >> On 21/12/17 17:12, Ville Syrjälä wrote: >> If the userspace knows this, then it knows which primary plane is for which crtc, right? And if it doesn't know this,

[Bug 101900] No HDMI HBR audio on Polaris (no TrueHD, no Atmos, no Neo:X, no HD Master audio) and static noise in sound when LPCM

https://bugs.freedesktop.org/show_bug.cgi?id=101900 --- Comment #18 from Direx --- (In reply to Michel Dänzer from comment #17) > FWIW, according to comments on https://lwn.net/Articles/740916/: > > * HDMI sinks complying with the relevant specs only accept Dolby

Re: Initial release of AMD Open Source Driver for Vulkan

Congratulations on getting this out the door It didn't compile for me without these changes: In pal: diff --git a/src/util/math.cpp b/src/util/math.cpp index 46e9ede..3af4259 100644 --- a/src/util/math.cpp +++ b/src/util/math.cpp @@ -54,7 +54,7 @@ static uint32 Float32ToFloatN(float f, const

[Bug 104143] r600/sb: clobbers gl_Position -> gl_FragCoord

https://bugs.freedesktop.org/show_bug.cgi?id=104143 --- Comment #10 from Emil Velikov --- Gert, should we close this considering the patch (fix?) has landed? -- You are receiving this mail because: You are the assignee for the

[Bug 104371] [amdgpu] Kernel oops on shutdown: unable to handle kernel paging request at virtual address

https://bugs.freedesktop.org/show_bug.cgi?id=104371 Bug ID: 104371 Summary: [amdgpu] Kernel oops on shutdown: unable to handle kernel paging request at virtual address Product: DRI Version: unspecified Hardware: x86-64

Re: [Bug 198123] Console is the wrong color at boot with radeon 6670

On 2017-12-19 11:48 AM, Michel Dänzer wrote: > On 2017-12-18 02:50 PM, Peter Rosin wrote: >> On 2017-12-18 12:37, Michel Dänzer wrote: >>> >>> Following up by e-mail, since I can't find Peter Rosin in the kernel >>> bugzilla. >>> >>> >>> On 2017-12-16 02:41 AM, bugzilla-dae...@bugzilla.kernel.org

Re: Initial release of AMD Open Source Driver for Vulkan

Hi No I'm not using ICC however that section prevents you using Clang, it basically says if not GCC then assumes Intel's compiler Cheers Mike On Fri, 22 Dec 2017, 3:04 pm Mao, David, wrote: > Hi Lothian, > Thanks for testing out out driver! > Officially we recommend you to

[PATCH] drm/ttm: fix double lock on glob->lru_lock

From: Colin Ian King Lock glob->lru_lock is locked before the while loop and also locked again at the end of the while loop; it appears that the lock at the end of the while loop is a double lock that should be removed. CoverityScan picked this up with the introduction

[PATCH 7/8] drm: Check that the plane supports the request format+modifier combo

From: Ville Syrjälä Currently we only check that the plane supports the pixel format of the fb we're about to feed to it. Extend it to check also the modifier, and more specifically that the combination of the format and modifier is supported. Cc:

Re: [PATCH] drm/ttm: fix double lock on glob->lru_lock

NAK,  ttm_bo_cleanup_refs() is dropping the lock. Your backtrace is cause by an issue I've fixed this morning on amd-staging-drm-next. Regards, Christian. Am 22.12.2017 um 19:03 schrieb Colin King: From: Colin Ian King Lock glob->lru_lock is locked before the

Re: [Mesa-dev] [ANNOUNCE] Wayland/Weston/Mesa HDR support (proof of concept)

On Thu, Dec 21, 2017 at 6:21 AM, Ville Syrjälä wrote: > Here's a quick proof of concept implementation of HDR support > for Wayland/Weston/Mesa. > > I'm not posting this as patches right now because I'm not sure > that would do much good given how rough this is. But

[PATCH] drm: Add DPCD definitions for DP 1.4 FEC feature

Forward Error Correction is supported on DP 1.4. This patch adds corresponding DPCD register definitions. v2: Add dri-devel mailing list to the CC list(Jani) v3: Change names, add missing masks (Manasi) Cc: dri-devel@lists.freedesktop.org Cc: Ville Syrjala Cc:

RE: drm/ast: Linux 4.14 AST DRM driver might not load gamma table [patch proposed]

Spoke too soon. Original patch worked better (adding call to DPMS ON event in commit call-back. Disregard the latest I sent. Apologies. > -Original Message- > From: Carroll, Lewis > Sent: Thursday, December 21, 2017 3:58 PM > To: dri-devel@lists.freedesktop.org > Cc: Wentland, Harry

[PULL] drm-intel-next

-next-2017-12-22 for you to fetch changes up to cfe4982ca488016d697cf0769ae70c9a78060c0d: drm/i915: Update DRIVER_DATE to 20171222 (2017-12-22 11:41:50 -0800) - Allow internal page allocation to fail (Chris) - More improvements

Re: [PATCH 1/2] drm/vc4: Add a mechanism to easily extend CL submissions

Boris Brezillon writes: > The number of attributes/objects you can pass to the > DRM_IOCTL_VC4_SUBMIT_CL ioctl is limited by the drm_vc4_submit_cl struct > size. > > Add a mechanism to easily pass extra attributes when submitting a CL to > the V3D engine. > >

Re: [PATCH 1/2] drm/vc4: Add a mechanism to easily extend CL submissions

On Fri, 22 Dec 2017 12:53:36 -0800 Eric Anholt wrote: > Boris Brezillon writes: > > > The number of attributes/objects you can pass to the > > DRM_IOCTL_VC4_SUBMIT_CL ioctl is limited by the drm_vc4_submit_cl struct > > size. > > > > Add a

[v4] drm: Add DPCD definitions for DP 1.4 FEC feature

Forward Error Correction is supported on DP 1.4. This patch adds corresponding DPCD register definitions. v2: Add dri-devel mailing list to the CC list(Jani) v3: Change names, add missing masks (Manasi) v4: Add missing shifts to mask (Manasi) Cc: dri-devel@lists.freedesktop.org Cc: Ville