https://bugs.freedesktop.org/show_bug.cgi?id=106355
--- Comment #4 from Norbert Klar ---
Care to tell me what's going on? 'Cause if it's duplicate of that bug, then it
wasn't fixed since then.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=103234
--- Comment #24 from Viktor Kecskes ---
(In reply to Marek Olšák from comment #23)
> The xorg ati driver is for the radeon kernel module.
> The xorg amdgpu driver is for the amdgpu kernel module.
>
> If the xorg
From: Dave Airlie
Although the kernel doesn't use this, qemu imports these headers
and it's best to keep them consistent.
This define is also something userspace may want to use.
Signed-off-by: Dave Airlie
---
include/uapi/linux/virtio_gpu.h | 1 +
1
On Wed, May 2, 2018 at 5:31 PM, John Stultz wrote:
> On Wed, May 2, 2018 at 5:01 PM, Alistair Strachan
> wrote:
>> This adds support for the chromiumos (not AOSP) version of minigbm. Like
>> hisi, the gralloc handle is not the same as the common
On Wed, May 2, 2018 at 5:01 PM, Alistair Strachan wrote:
> This adds support for the chromiumos (not AOSP) version of minigbm. Like
> hisi, the gralloc handle is not the same as the common libdrm handle
> (just yet), so we do need a separate backend for now.
>
> Tested with
On Wed, May 2, 2018 at 4:56 PM, Alistair Strachan wrote:
> Use of the sw_sync API is not allowed any more. Until drm_hwcomposer is
> weaned off of sw_sync, build our own copy.
>
> Cc: John Stultz
> Cc: Rob Herring
> Cc: Sean
On Wed, May 2, 2018 at 4:56 PM, Alistair Strachan wrote:
> In commit d12274d, "drm_hwcomposer: Rework platformdrmgeneric.cpp
> to use libdrm's gralloc handle", the use of drm_gralloc was removed.
>
> Cc: John Stultz
> Cc: Rob Herring
On Wed, May 2, 2018 at 4:55 PM, Alistair Strachan wrote:
> After commit 94bb596, the tests for drm_hwcomposer no longer build,
> because the build system detects that they are linking other vendor
> modules (but installing themselves elsewhere).
>
> This change also adds the
On Wed, May 2, 2018 at 4:53 PM, Alistair Strachan wrote:
> Commit 0f7487f "drm_hwcomposer: remove NVIDIA importer" removed most of
> the implementation, but not the platformnv.h header file. Remove this
> header now.
>
> Cc: John Stultz
> Cc: Rob
Currently; we're grabbing all of the modesetting locks before adding MST
connectors to fbdev. This isn't actually necessary, and causes a
deadlock as well:
==
WARNING: possible circular locking dependency detected
4.17.0-rc3Lyude-Test+ #1
https://bugs.freedesktop.org/show_bug.cgi?id=105072
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
---
https://bugs.freedesktop.org/show_bug.cgi?id=104347
Timothy Arceri changed:
What|Removed |Added
Summary|AMD RX 580: Hide/Show |AMD RX 580:
https://bugs.freedesktop.org/show_bug.cgi?id=104347
Timothy Arceri changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=106355
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.freedesktop.org/show_bug.cgi?id=100802
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
---
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #21 from Francisco Pina Martins ---
Created attachment 139288
--> https://bugs.freedesktop.org/attachment.cgi?id=139288=edit
journalctl log with KASAN_OUTLINE and kasan_multi_shot using a kernel compiled
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #14 from Timothy Pearson ---
(In reply to Andrey Grodzovsky from comment #13)
> (In reply to Timothy Pearson from comment #11)
> > We could get you direct access to test hardware if that would help.
https://bugs.freedesktop.org/show_bug.cgi?id=106363
Bug ID: 106363
Summary: Powerplay support for SI asics
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #13 from Andrey Grodzovsky ---
(In reply to Timothy Pearson from comment #11)
> We could get you direct access to test hardware if that would help.
> Basically, these systems are completely controllable
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #12 from Andrey Grodzovsky ---
(In reply to Timothy Pearson from comment #11)
> We could get you direct access to test hardware if that would help.
> Basically, these systems are completely controllable
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #68 from MirceaKitsune ---
Created attachment 139283
--> https://bugs.freedesktop.org/attachment.cgi?id=139283=edit
Output of: watch --interval 0.1 sensors
(In reply to H4nN1baL from comment
On Wed, May 02, 2018 at 04:12:18PM -0400, Sean Paul wrote:
> On Wed, May 02, 2018 at 03:46:21PM +0200, Thomas Hellstrom wrote:
> > From: Dirk Hohndel
> >
> > This is dual licensed under GPL-2.0 or MIT.
> >
> > Cc: "Christian König"
> > Signed-off-by:
On Fri, 9 Mar 2018 15:32:56 -0800
Eric Anholt wrote:
> In the cleanup, I didn't notice that we needed to dereference the
> connector for the bus_format. Fix the regression by looking up the
> first (and only) connector attached to us, and assume that its
> bus_format is what
On Wed, May 02, 2018 at 03:46:21PM +0200, Thomas Hellstrom wrote:
> From: Dirk Hohndel
>
> This is dual licensed under GPL-2.0 or MIT.
>
> Cc: "Christian König"
> Signed-off-by: Dirk Hohndel (VMware)
> Signed-off-by: Thomas
On Fri, Apr 20, 2018 at 08:51:59AM +0200, Daniel Vetter wrote:
> With the ioctl and driver prep done, we can remove everything else.
>
> Signed-off-by: Daniel Vetter
> Cc: Gustavo Padovan
> Cc: Maarten Lankhorst
>
On Fri, Mar 09, 2018 at 03:32:56PM -0800, Eric Anholt wrote:
> In the cleanup, I didn't notice that we needed to dereference the
> connector for the bus_format. Fix the regression by looking up the
> first (and only) connector attached to us, and assume that its
> bus_format is what we want.
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #11 from Timothy Pearson ---
We could get you direct access to test hardware if that would help. Basically,
these systems are completely controllable via BMC, so we could give remote
access to a
Hi Dave,
A couple of CS 101 "Gotcha!" fixes for you this week. One for a reference count,
and one for a memory leak. Both are cc: stable.
drm-misc-fixes-2018-05-02:
vc4: Fix bo refcounts during async commits (Boris)
vga-dac: Fix edid memory leak (Sean)
Cc: Boris Brezillon
https://bugs.freedesktop.org/show_bug.cgi?id=103234
--- Comment #23 from Marek Olšák ---
The xorg ati driver is for the radeon kernel module.
The xorg amdgpu driver is for the amdgpu kernel module.
If the xorg driver is missing for the respective kernel module, the X server
On Fri, Apr 20, 2018 at 02:59:59PM -0400, Sean Paul wrote:
> edid should be freed once it's finished being used.
>
> Fixes: 56fe8b6f4991 ("drm/bridge: Add RGB to VGA bridge support")
> Cc: Rob Herring
> Cc: Sean Paul
> Cc: Maxime Ripard
On Wed, May 02, 2018 at 10:02:01AM +0530, Sandeep Panda wrote:
> Add support for Innolux TV123WAM, which is a 12.3" eDP
> display panel with 2160x1440 resolution.
>
> Signed-off-by: Sandeep Panda
> ---
> drivers/gpu/drm/panel/panel-simple.c | 27
On Wed, May 02, 2018 at 10:01:59AM +0530, Sandeep Panda wrote:
> Add support for TI's sn65dsi86 dsi2edp bridge chip.
> The chip converts DSI transmitted signal to eDP signal,
> which is fed to the connected eDP panel.
>
> This chip can be controlled via either i2c interface or
> dsi interface.
From: Ville Syrjälä
Clear the old_state and new_state pointers for every object in
drm_atomic_state_default_clear(). Otherwise
drm_atomic_get_{new,old}_*_state() will hand out stale pointers to
anyone who hasn't first confirmed that the object is in fact part of
Eric Anholt writes:
> In the cleanup, I didn't notice that we needed to dereference the
> connector for the bus_format. Fix the regression by looking up the
> first (and only) connector attached to us, and assume that its
> bus_format is what we want. Some day it would be good
On 2018-05-02 06:21 PM, Christoph Hellwig wrote:
> On Wed, May 02, 2018 at 04:31:09PM +0200, Michel Dänzer wrote:
>>> No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface
>>> for dma allocations and just cause problems. I actually plan to
>>> get rid of the gfp_t argument in
Daniel Vetter writes:
> This came up in discussions when reviewing drm patches.
>
> Cc: Eric Anholt
> Cc: linux-...@vger.kernel.org
> Cc: Jonathan Corbet
> Signed-off-by: Daniel Vetter
>
> --
>
> Aside: I wonder
Daniel Vetter writes:
> Noticed while I was typing docs. Entirely unused.
>
> v2: Remove reference in @timeline_value_str too. While at it clarify
> why timeline_value_str has a fence parameter - we don't have an
> explicit timeline structure unfortunately.
>
> Cc: Eric
https://bugs.freedesktop.org/show_bug.cgi?id=106194
--- Comment #8 from Shmerl ---
Is this happening in 4.17rc3?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
Hi Maxime,
You don't have to handcode the fragments anymore with the new syntax,
and U-Boot makes it really trivial to use if you use the FIT image
format to have multiple overlays bundled in the same image. You can
choose to apply them dynamically, for example based on an EEPROM or
some other
On Wed, May 02, 2018 at 04:31:09PM +0200, Michel Dänzer wrote:
> > No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface
> > for dma allocations and just cause problems. I actually plan to
> > get rid of the gfp_t argument in dma_alloc_attrs sooner, and only
> > allow either
Quoting Chris Wilson (2018-05-02 10:46:07)
> Quoting Matthias Kaehlcke (2018-05-01 19:24:40)
> > Commit 39bf4de89ff7 ("drm/i915: Add -Wall -Wextra to our build, set
> > warnings to full") enabled extra warnings for i915 to spot possible
> > bugs in new code, and then disabled a subset of these
https://bugs.freedesktop.org/show_bug.cgi?id=106355
--- Comment #2 from Norbert Klar ---
Yep, except in my case, it's only happening with Chromium.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106355
--- Comment #1 from Timothy Arceri ---
Looks a bit like bug 105910
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On 2018-05-02 10:43 AM, Colin King wrote:
> From: Colin Ian King
>
> The declaration of pointer amdgpu_crtc has a redundant assignment to
> amdgpu_crtc. Clean this up by removing it.
>
> Detected by CoverityScan, CID#1460299 ("Evaluation order violation")
>
>
On Wed, Apr 25, 2018 at 11:07:57AM +0200, Daniel Vetter wrote:
> It's going away.
>
> Signed-off-by: Daniel Vetter
Reviewed-by: Sean Paul
> Cc: Rob Clark
> Cc: Jordan Crouse
> Cc: Nicolas Dechesne
On Fri, Apr 20, 2018 at 08:51:58AM +0200, Daniel Vetter wrote:
> Control nodes are no more!
>
> Signed-off-by: Daniel Vetter
Reviewed-by: Sean Paul
> Cc: VMware Graphics
> Cc: Sinclair Yeh
On Fri, Apr 20, 2018 at 08:51:57AM +0200, Daniel Vetter wrote:
> Control nodes are no more!
>
> Signed-off-by: Daniel Vetter
Reviewed-by: Sean Paul
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
On Fri, Apr 20, 2018 at 08:51:56AM +0200, Daniel Vetter wrote:
> We've disabled control nodes in
>
> commit 8a357d10043c75e980e7fcdb60d2b913491564af
> Author: Daniel Vetter
> Date: Fri Oct 28 10:10:50 2016 +0200
>
> drm: Nerf DRM_CONTROL nodes
>
> and there was
https://bugs.freedesktop.org/show_bug.cgi?id=106355
Michel Dänzer changed:
What|Removed |Added
QA Contact|mesa-dev@lists.freedesktop.
From: Colin Ian King
The declaration of pointer amdgpu_crtc has a redundant assignment to
amdgpu_crtc. Clean this up by removing it.
Detected by CoverityScan, CID#1460299 ("Evaluation order violation")
Signed-off-by: Colin Ian King
---
On 05/02/2018 04:00 PM, Christian König wrote:
Am 02.05.2018 um 15:46 schrieb Thomas Hellstrom:
From: Dirk Hohndel
This is dual licensed under GPL-2.0 or MIT.
Cc: "Christian König"
Signed-off-by: Dirk Hohndel (VMware)
On 2018-05-02 02:41 PM, Christoph Hellwig wrote:
> On Wed, May 02, 2018 at 02:18:56PM +0200, Daniel Vetter wrote:
>> Other dma-api backends like cma just shut up when __GFP_NOWARN is
>> passed. And afaiui Christoph Hellwig has plans to nuke the DMA_ATTR
>> stuff (or at least clean it up) - should
Hi Dave,
Just the addition of Geminilake MODULE_FIRMWARE for DMC now when it's in
linux-firmware.git.
Regards, Joonas
drm-intel-fixes-2018-05-02:
Add DMC firmware for Geminilake.
The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64:
Linux v4.17-rc3 (2018-04-29
Am 02.05.2018 um 15:46 schrieb Thomas Hellstrom:
From: Dirk Hohndel
This is dual licensed under GPL-2.0 or MIT.
Cc: "Christian König"
Signed-off-by: Dirk Hohndel (VMware)
Signed-off-by: Thomas Hellstrom
The Versatile Express uses a special configuration controller
deeply embedded in the system motherboard FPGA to multiplex the
two to three (!) display controller instances out to the single
SiI9022 bridge.
Set up an extra file with the logic to probe to the FPGA mux
register on the system
The Versatile Express has 8 MB of dedicated video RAM (VRAM)
on the motherboard, which is what we should be using for the
PL111 if available. On this platform, the memory backplane
is constructed so that only this memory will work properly
with the CLCD on the motherboard, using any other memory
From: Dirk Hohndel
This is dual licensed under GPL-2.0 or MIT.
Cc: "Christian König"
Signed-off-by: Dirk Hohndel (VMware)
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/ttm/ttm_agp_backend.c | 1 +
On 04/27/18 17:25, Rob Herring wrote:
> On Thu, Apr 26, 2018 at 10:48:22PM +0300, Jyri Sarha wrote:
>> Add support for Three Five displays TFC S9700RTWV43TR-01B 800x480
>> panel with resistive touch found on TI's AM335X-EVM.
>>
>> Signed-off-by: Jyri Sarha
>> Reviewed-by: Tomi
On Tue, May 01, 2018 at 03:24:11PM +0200, Michel Dänzer wrote:
> From: Michel Dänzer
>
> The result was printing the warning only when we were explicitly asked
> not to.
Thanks, applied to the dma-mapping tree for 4.17.
___
On Wed, May 02, 2018 at 02:18:56PM +0200, Daniel Vetter wrote:
> Other dma-api backends like cma just shut up when __GFP_NOWARN is
> passed. And afaiui Christoph Hellwig has plans to nuke the DMA_ATTR
> stuff (or at least clean it up) - should we just remove
> DMA_ATTR_NO_WARN and instead only
On Wed, May 2, 2018 at 1:27 AM, Jagan Teki wrote:
> Hi Rob,
>
> On Tue, May 1, 2018 at 9:49 PM, Rob Herring wrote:
>>
>> On Mon, Apr 30, 2018 at 05:10:45PM +0530, Jagan Teki wrote:
>> > HDMI PHY on Allwinner A64 has similar like H3/H5.
>> >
>> >
On Wed, May 2, 2018 at 11:49 AM, Christian König
wrote:
> Am 01.05.2018 um 15:24 schrieb Michel Dänzer:
>>
>> From: Michel Dänzer
>>
>> The result was printing the warning only when we were explicitly asked
>> not to.
>>
>> Cc:
From: Stanislav Lisovskiy
Added encoding of drm content_type property from drm_connector_state
within AVI infoframe in order to properly handle external HDMI TV
content-type setting.
This requires also manipulationg ITC bit, as stated in
HDMI spec.
v2:
* Moved
From: Stanislav Lisovskiy
Added content type setting property to drm_connector(part 1)
and enabled transmitting it with HDMI AVI infoframes
for i915(part 2).
Stanislav Lisovskiy (2):
drm: content-type property for HDMI connector
i915: content-type property for
From: Stanislav Lisovskiy
Added content_type property to drm_connector_state
in order to properly handle external HDMI TV content-type setting.
v2:
* Moved helper function which attaches content type property
to the drm core, as was suggested.
Removed
Hi Andres,
sorry for the delayed response. First on vacation and now on sick leave :(
Please see below.
Am 20.04.2018 um 21:35 schrieb Andres Rodriguez:
Ping.
On 2018-04-17 06:12 PM, Andres Rodriguez wrote:
Add a new function amdgpu_ucode_request_firmware() that encapsulates a
lot of the
On Wed, May 02, 2018 at 07:34:21PM +0800, Icenowy Zheng wrote:
>
>
> 于 2018年5月2日 GMT+08:00 下午7:32:50, Maxime Ripard 写到:
> >On Mon, Apr 30, 2018 at 05:10:39PM +0530, Jagan Teki wrote:
> >> DE2 in A64 has clock control unit and behavior is
> >> same like H3/H5, so reuse
On Mon, Apr 30, 2018 at 05:10:52PM +0530, Jagan Teki wrote:
> From: Icenowy Zheng
>
> Allwinner SoCs with DWC HDMI controller have a "HVCC" power pin for the
> HDMI part, and on some boards it's connected to a dedicated regulator
> rather than the main 3.3v.
>
> Add support for
Hi,
On Mon, Apr 30, 2018 at 05:10:46PM +0530, Jagan Teki wrote:
> + hdmi_phy: hdmi-phy@1ef {
> + compatible = "allwinner,sun50i-a64-hdmi-phy",
> + "allwinner,sun8i-h3-hdmi-phy";
> + reg = <0x01ef
On Mon, Apr 30, 2018 at 05:10:39PM +0530, Jagan Teki wrote:
> DE2 in A64 has clock control unit and behavior is
> same like H3/H5, so reuse the same in A64.
>
> Signed-off-by: Jagan Teki
> ---
> arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 15 +++
> 1
On Wed, 2018-05-02 at 13:08 +0200, Daniel Vetter wrote:
> On Wed, May 02, 2018 at 09:08:11AM +, Lisovskiy, Stanislav wrote:
> > On Wed, 2018-05-02 at 10:15 +0200, Daniel Vetter wrote:
> > > >
> > >
> > > On Wed, May 02, 2018 at 08:09:24AM +, Lisovskiy, Stanislav
> > > wrote:
> > > > On
On Wed, May 02, 2018 at 11:10:48AM +0100, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in DRM_ERROR error message
>
> Signed-off-by: Colin Ian King
Applied to drm-misc-next, thanks.
-Daniel
> ---
>
On Wed, May 02, 2018 at 09:08:11AM +, Lisovskiy, Stanislav wrote:
> On Wed, 2018-05-02 at 10:15 +0200, Daniel Vetter wrote:
> > >
> > On Wed, May 02, 2018 at 08:09:24AM +, Lisovskiy, Stanislav wrote:
> > > On Mon, 2018-04-30 at 17:00 +0200, Daniel Vetter wrote:
> > > > On Fri, Apr 27,
Hi Geert
On 02/05/18 09:59, Geert Uytterhoeven wrote:
> Hi Laurent,
>
> On Sat, Apr 28, 2018 at 12:43 AM, Laurent Pinchart
> wrote:
>> On Saturday, 28 April 2018 01:21:49 EEST Kieran Bingham wrote:
>>> The r8a77965 M3-N platform supports a DPAD, HDMI and LVDS
From: Colin Ian King
Trivial fix to spelling mistake in DRM_ERROR error message
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/sti/sti_crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #67 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #63)
> (In reply to iive from comment #62)
>
> I booted my machine with the kernel parameter panic=30 as instructed. I then
> waited for over two minutes to see if
Am 01.05.2018 um 15:24 schrieb Michel Dänzer:
From: Michel Dänzer
The result was printing the warning only when we were explicitly asked
not to.
Cc: sta...@vger.kernel.org
Fixes: 0176adb004065d6815a8e67946752df4cd947c5b "swiotlb: refactor
coherent buffer allocation"
Quoting Matthias Kaehlcke (2018-05-01 19:24:40)
> Commit 39bf4de89ff7 ("drm/i915: Add -Wall -Wextra to our build, set
> warnings to full") enabled extra warnings for i915 to spot possible
> bugs in new code, and then disabled a subset of these warnings to keep
> the current code building without
https://bugs.freedesktop.org/show_bug.cgi?id=106258
Dan Horák changed:
What|Removed |Added
CC||bcroc...@redhat.com
---
If get_scale_coef functions fail, they return NULL, but we never check
the return value and could do a NULL deref. This should not happen as we
ought to validate the amount of scaling already earlier, but to be safe,
add the necessary check.
Signed-off-by: Tomi Valkeinen
Hi,
This series has some minor fixes found by a static analysis tool, and one for
missing linefeeds. As far as I know, we have never hit any of those errors.
Tomi
Tomi Valkeinen (4):
drm/omap: check return value from soc_device_match
drm/omap: handle error if scale coefs are not found
Handle memory allocation failures in omap_connector to avoid NULL
derefs.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/omap_connector.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/omapdrm/omap_connector.c
A bunch of debug and error prints are missing linefeeds. Add those.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dispc.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/omapdrm/dss/dispc.c
soc_device_match() can return NULL, so add a check and fail if
soc_device_match() fails.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/hdmi4_core.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
On Wed, 2018-05-02 at 10:15 +0200, Daniel Vetter wrote:
> >
> On Wed, May 02, 2018 at 08:09:24AM +, Lisovskiy, Stanislav wrote:
> > On Mon, 2018-04-30 at 17:00 +0200, Daniel Vetter wrote:
> > > On Fri, Apr 27, 2018 at 10:40:00PM +0300, Ville Syrjälä wrote:
> > > > On Mon, Apr 23, 2018 at
https://bugs.freedesktop.org/show_bug.cgi?id=106225
--- Comment #20 from Michel Dänzer ---
Now I notice there's another report for firmware_parser_create+0xa9b/0xd90.
What does faddr2line say for that?
Though it's weird that KASAN claims the memory written in
Hi,
On 18/04/18 17:29, Dan Carpenter wrote:
> Smatch complains that "area_free" could be used without being
> initialized. This code is several years old and premusably works fine
> so this can't be a very serious bug. But it's easy enough to silence
> the warning. If "area_free" is false at
Hi Laurent,
On Sat, Apr 28, 2018 at 12:43 AM, Laurent Pinchart
wrote:
> On Saturday, 28 April 2018 01:21:49 EEST Kieran Bingham wrote:
>> The r8a77965 M3-N platform supports a DPAD, HDMI and LVDS output, along
>> 3 DU channels. However, DU2 is not available in
On 02/05/18 10:24, Dariusz Marcinkiewicz wrote:
> Hello, pretty late here but I have a small comment.
>
>
>> From: Hans Verkuil
>
>> This adds support for the DisplayPort CEC-Tunneling-over-AUX
>> feature that is part of the DisplayPort 1.3 standard.
>
>
>> +int
Noticed while I was typing docs. Entirely unused.
v2: Remove reference in @timeline_value_str too. While at it clarify
why timeline_value_str has a fence parameter - we don't have an
explicit timeline structure unfortunately.
Cc: Eric Anholt
Reviewed-by: Christian König
The trivial enable_signaling implementation matches the default code.
v2: Fix up commit message to match patch better (Eric).
Cc: Eric Anholt
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: Dave Airlie
The trivial enable_signaling implementation matches the default code.
v2: Fix up commit message to match patch better (Eric).
Cc: Eric Anholt
Reviewed-by: Eric Anholt
Signed-off-by: Daniel Vetter
Cc: Dave Airlie
On Wed, May 02, 2018 at 08:09:24AM +, Lisovskiy, Stanislav wrote:
> On Mon, 2018-04-30 at 17:00 +0200, Daniel Vetter wrote:
> > On Fri, Apr 27, 2018 at 10:40:00PM +0300, Ville Syrjälä wrote:
> > > On Mon, Apr 23, 2018 at 10:34:41AM +0300, StanLis wrote:
> > > > From: Stanislav Lisovskiy
On Mon, 2018-04-30 at 17:00 +0200, Daniel Vetter wrote:
> On Fri, Apr 27, 2018 at 10:40:00PM +0300, Ville Syrjälä wrote:
> > On Mon, Apr 23, 2018 at 10:34:41AM +0300, StanLis wrote:
> > > From: Stanislav Lisovskiy
> > >
> > > Added content_type property to
On 2018-04-29 01:56 AM, Ilia Mirkin wrote:
> On Sat, Apr 28, 2018 at 7:02 PM, Michel Dänzer wrote:
>>
>> Unfortunately, there was an swiotlb regression (not directly related to
>> Christian's work) shortly after this fix, also in 4.16-rc1, which is now
>> fixed in 4.17-rc1 and
On Wed, May 02, 2018 at 12:20:19PM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> If the user-space does not support aspect-ratio, and requests for a
> modeset with mode having aspect ratio bits set, then the given
> user-mode must be rejected. Secondly,
On Wed, May 02, 2018 at 12:20:18PM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> To enable aspect-ratio support in DRM, blindly exposing the aspect
> ratio information along with mode, can break things in existing
> non-atomic user-spaces which have no
This came up in discussions when reviewing drm patches.
Cc: Eric Anholt
Cc: linux-...@vger.kernel.org
Cc: Jonathan Corbet
Signed-off-by: Daniel Vetter
--
Aside: I wonder whether we shouldn't move this to some other place and
rst-ify
https://bugs.freedesktop.org/show_bug.cgi?id=105733
--- Comment #13 from emmanuel.boudrea...@polymtl.ca ---
I seem to have this same issue when opening an e-mail with a certain picture
using emacs. I'm using ArchLinux and Wayland (gnome shell). It is very easy to
reproduce so let me know if more
On Tue, May 01, 2018 at 10:58:45AM -0700, Eric Anholt wrote:
> Signed-off-by: Eric Anholt
> ---
>
> airlied + danvet: this is the last change I think we need before I can
> merge v3d with your acks. Sending as a diff so you don't have to look
> at the whole thing again. Look
1 - 100 of 127 matches
Mail list logo