https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #2 from fin4...@hotmail.com ---
I am tired to automatic monitor sleep problems and made a launcher to manually
sleep the monitor.
#! /bin/bash
sleep 5s
xset dpms force standby
--
You are receiving this mail because:
You are the as
On Mon, Jan 07, 2019 at 05:43:22PM +0100, Noralf Trønnes wrote:
> Den 07.01.2019 11.22, skrev Daniel Vetter:
> > The current one essentially means you need CMA or a vmalloc backed
> > object, which makes fbdev emulation a special case.
> >
> > Since implementing this will be quite a bit of work, c
On Mon, Jan 07, 2019 at 07:56:47PM -0500, Lyude Paul wrote:
> Since I've had to fix two cases of drivers not checking the return code
> from this function, let's make the compiler complain so this doesn't
> come up again in the future.
>
> Signed-off-by: Lyude Paul
> Cc: Jerry Zuo
> Cc: Daniel V
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #6 from fin4...@hotmail.com ---
Arch Linux distributions is for nvidia gpus. Use Debian testing/sid Xfce and
Oibaf ppa Mesa cosmic version. The AMD wip kernel is the best kernel for AMD
GPUs
https://cgit.freedesktop.org/~agd5f/linux/l
On Tue, Jan 08, 2019 at 12:23:52PM +0500, Ivan Mironov wrote:
> SDL 1.2 sets all fields related to the pixel format to zero in some
> cases[1]. Prior to commit db05c48197759 ("drm: fb-helper: Reject all
> pixel format changing requests"), there was an unintentional workaround
> for this that existe
Needs just a few additional includes here and there.
Cc: Sam Ravnborg
Cc: Daniel Vetter
Cc: Laurent Pinchart
Acked-by: Daniel Vetter
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/dvo.h | 1 -
drivers/gpu/drm/i915/i915_drv.c| 1 -
drivers/gpu/drm/i915/i915_dr
On 07.01.2019 22:56, Daniel Vetter wrote:
> On Mon, Jan 7, 2019 at 5:27 PM Andrzej Hajda wrote:
>> On 07.01.2019 17:08, Daniel Vetter wrote:
>>> On Mon, Jan 07, 2019 at 12:26:58PM +0100, Andrzej Hajda wrote:
On 07.01.2019 11:45, Daniel Vetter wrote:
> On Thu, Jan 03, 2019 at 01:11:47PM +0
On Tue, Jan 08, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In function
> 'amdgpu_dm_mode_config_init':
> drive
This patch series enables HDR support in drm. It basically defines
HDR metadata structures, property to pass content (after blending)
metadata from user space compositors to driver.
Dynamic Range and Mastering infoframe creation and sending.
ToDo:
1. We need to get the color framework in place fo
On 2019-01-07 09:40, Geert Uytterhoeven wrote:
> Hi Peter,
>
> On Mon, Jan 7, 2019 at 9:26 AM Peter Rosin wrote:
>> On 2019-01-06 10:33, Geert Uytterhoeven wrote:
>>> On Mon, Nov 26, 2018 at 10:59 PM Peter Rosin wrote:
If there are extra logos (CONFIG_FB_LOGO_EXTRA) the heights of these
>>>
On Tue, Jan 8, 2019 at 9:35 AM Andrzej Hajda wrote:
> On 07.01.2019 22:56, Daniel Vetter wrote:
> > On Mon, Jan 7, 2019 at 5:27 PM Andrzej Hajda wrote:
> >> On 07.01.2019 17:08, Daniel Vetter wrote:
> >>> On Mon, Jan 07, 2019 at 12:26:58PM +0100, Andrzej Hajda wrote:
> On 07.01.2019 11:45, D
On Mon, Jan 7, 2019 at 4:14 PM kbuild test robot wrote:
>
> Hi Vivek,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v5.0-rc1 next-20190107]
> [if your patch is applied to the wrong git tree, please drop us a note to
On Mon, 2019-01-07 at 11:08 +0100, Daniel Vetter wrote:
> > > > @@ -1654,6 +1712,40 @@ int drm_fb_helper_check_var(struct
> > > > fb_var_screeninfo *var,
> > > > return -EINVAL;
> > > > }
> > > >
> > > > + /*
> > > > +* Workaround for SDL 1.2, which is known
On 2019-01-06 10:33, Geert Uytterhoeven wrote:
> Hi Peter,
>
> On Mon, Nov 26, 2018 at 10:59 PM Peter Rosin wrote:
>> If there are extra logos (CONFIG_FB_LOGO_EXTRA) the heights of these
>> extra logos are not considered when centering the first logo vertically.
>>
>> Signed-off-by: Peter Rosin
After mapping a sg list the we should use sg_dma_address() and
sg_dma_len() macros to access sg->address and sg->length. Fix
the same for sg->length in drm_prime_sg_to_page_addr_arrays().
Signed-off-by: Vivek Gautam
---
Changes since v1:
- Fixed compilation error: replaced sg_dma_length() with
CEA 861.3 spec adds colorimetry data block for HDMI.
Parsing the block to get the colorimetry data from
panel.
v2: Rebase
v3: No Change
v4: Addressed Shashank's review comments. Updated
colorimetry field to 16 bit as DCI-P3 got added
in CEA 861-G spec, as pointed out by Shashank.
Signed-off-by:
Hi Rob,
On Mon, Jan 7, 2019 at 9:11 PM Mathieu Malaterre wrote:
>
> On Mon, Jan 7, 2019 at 6:31 PM Rob Herring wrote:
> >
> > Commit 5c63e407aaab ("fbdev: Convert to using %pOFn instead of
> > device_node.name") changed how the OF FB driver handles the OF node
> > name. This missed the case wher
This patch adds a blob property to get HDR metadata
information from userspace. This will be send as part
of AVI Infoframe to panel.
v2: Rebase and modified the metadata structure elements
as per Ville's POC changes.
v3: No Change
v4: Addressed Shashank's review comments
Signed-off-by: Uma Shan
On (12/20/18 17:31), Bartlomiej Zolnierkiewicz wrote:
[..]
> > +++ b/kernel/printk/printk.c
> > @@ -66,6 +66,7 @@ int console_printk[4] = {
> > CONSOLE_LOGLEVEL_MIN, /* minimum_console_loglevel */
> > CONSOLE_LOGLEVEL_DEFAULT, /* default_console_loglevel */
> > };
> > +EXPO
HDR metadata block is introduced in CEA-861.3 spec.
Parsing the same to get the panel's HDR metadata.
v2: Rebase and added Ville's POC changes to the patch.
v3: No Change
v4: Addressed Shashank's review comments
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/drm_connector.c | 2 +-
drivers/g
Attach HDR metadata property to connector object.
v2: Rebase
v3: Updated the property name as per updated name
while creating hdr metadata property
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_
SDL 1.2 sets all fields related to the pixel format to zero in some
cases[1]. Prior to commit db05c48197759 ("drm: fb-helper: Reject all
pixel format changing requests"), there was an unintentional workaround
for this that existed for more than a decade. First in device-specific DRM
drivers, then h
When creating frame buffer, userspace may request to attach to a
previously allocated GEM object that is smaller than what GPU
requires. Validation must be done to prevent out-of-bound DMA,
otherwise it could be exploited to reveal sensitive data.
This fix is not done in a common code path because
After mapping a sg list we should use sg_dma_address(), and
sg_dma_len() macros to access sg->address and sg->length. Fix
the same for sg->length in drm_prime_sg_to_page_addr_arrays().
Signed-off-by: Vivek Gautam
---
This came while debugging one dmabuf import issue that we are seeing
on sdm845
I submitted the bug report at
https://bugs.freedesktop.org/show_bug.cgi?id=109245 . The dmesg log is
attached to the bug report.
Daniel
On Mon, 7 Jan 2019 at 14:34, Ville Syrjälä
wrote:
>
> On Sat, Jan 05, 2019 at 12:47:12AM +0100, Daniel Kamil Kozar wrote:
> > Hello.
> > After upgrading the ker
On 2019-01-07 10:11, Geert Uytterhoeven wrote:
> Hi Peter,
>
> On Mon, Jan 7, 2019 at 10:03 AM Peter Rosin wrote:
>> On 2019-01-07 09:59, Peter Rosin wrote:
>>> On 2019-01-07 09:40, Geert Uytterhoeven wrote:
On Mon, Jan 7, 2019 at 9:26 AM Peter Rosin wrote:
> On 2019-01-06 10:33, Geert
Hello Sam,
On 2/1/19 22:37, Sam Ravnborg wrote:
> The problem with the RED/BLUE lines swapped is something I
> have encountered while working with DRM support for Atmel at91sam9263 too.
>
> The solution selected is to extend the endpoint with
> a new optional property:
>
> - wiring: Wiring of da
Userspace may request pitch alignment that is not supported by GPU.
Some requests 32, but GPU ignores it and uses default 64 when cpp is
4. If GEM object is allocated based on the smaller alignment, GPU
DMA will go out of bound.
Cc: sta...@vger.kernel.org # v4.2+
Signed-off-by: Yu Zhao
---
drive
On Mon, Jan 7, 2019 at 6:31 PM Rob Herring wrote:
>
> Commit 5c63e407aaab ("fbdev: Convert to using %pOFn instead of
> device_node.name") changed how the OF FB driver handles the OF node
> name. This missed the case where the node name is passed to
> offb_init_palette_hacks(). This results in a NU
Strict requirement of pixclock to be zero breaks support of SDL 1.2
which contains hardcoded table of supported video modes with non-zero
pixclock values[1].
To better understand which pixclock values are considered valid and how
driver should handle these values, I briefly examined few existing f
This patch implements get() and set() functions for HDR output
metadata property.The blob data is received from userspace and
saved in connector state, the same is returned as blob in get
property call to userspace.
v2: Rebase and added Ville's POC changes
v3: No Change
v4: Addressed Shashank's
On 2019-01-07 09:59, Peter Rosin wrote:
> On 2019-01-07 09:40, Geert Uytterhoeven wrote:
>> Hi Peter,
>>
>> On Mon, Jan 7, 2019 at 9:26 AM Peter Rosin wrote:
>>> On 2019-01-06 10:33, Geert Uytterhoeven wrote:
On Mon, Nov 26, 2018 at 10:59 PM Peter Rosin wrote:
> If there are extra logos
Hardware may have HDR capability on certain plane
engines. Enabling the same in drm plane structure
so that this can be communicated to user space.
Each drm driver should set this flag to true for planes
which support HDR.
v2: Rebase
Signed-off-by: Uma Shankar
---
include/drm/drm_plane.h | 3 +
From: Ville Syrjälä
This is to limit PORT C on GLK to drive only
HDMI. Not sure if this is mandatory, this is just
to test HDR on GLK HDMI.
Signed-off-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_bios.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/
Enable writing of HDR metadata infoframe to panel.
The data will be provid by usersapace compositors, based
on blending policies and passsed to driver through a blob
property.
v2: Rebase
v3: Fixed a warning message
v4: Addressed Shashank's review comments
Signed-off-by: Uma Shankar
---
driver
Enable Dynamic Range and Mastering Infoframe for HDR
content, which is defined in CEA 861.3 spec.
The metadata will be computed based on blending
policy in userspace compositors and passed as a connector
property blob to driver. The same will be sent as infoframe
to panel which support HDR.
v2: R
This patch enables modeset whenever HDR metadata
needs to be updated to sink.
Signed-off-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_atomic.c | 15 ++-
drivers/gpu/drm/i915/intel_hdmi.c | 4
2 files changed, 18 insertions(+), 1 deletion(-)
di
From: Ville Syrjälä
ADD HLG EOTF to the list of EOTF transfer functions supported.
Hybrid Log-Gamma (HLG) is a high dynamic range (HDR) standard.
HLG defines a nonlinear transfer function in which the lower
half of the signal values use a gamma curve and the upper half
of the signal values use a
From: Ville Syrjälä
This patch enables infoframes on GLK+ to be
used to send HDR metadata to HDMI sink.
v2: Addressed Shashank's review comment.
Signed-off-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/i915_reg.h | 4
drivers/gpu/drm/i915/intel_hdmi.c | 13 +++
On Mon, Jan 07, 2019 at 08:48:21PM +0530, Jagan Teki wrote:
> On Mon, Jan 7, 2019 at 7:42 PM Maxime Ripard
> wrote:
> >
> > On Fri, Dec 21, 2018 at 02:26:11AM +0530, Jagan Teki wrote:
> > > On Tue, Dec 11, 2018 at 10:19 PM Maxime Ripard
> > > wrote:
> > > >
> > > > On Mon, Dec 10, 2018 at 09:47:
https://bugs.freedesktop.org/show_bug.cgi?id=109246
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
On 08.01.2019 09:47, Daniel Vetter wrote:
> On Tue, Jan 8, 2019 at 9:35 AM Andrzej Hajda wrote:
>> On 07.01.2019 22:56, Daniel Vetter wrote:
>>> On Mon, Jan 7, 2019 at 5:27 PM Andrzej Hajda wrote:
On 07.01.2019 17:08, Daniel Vetter wrote:
> On Mon, Jan 07, 2019 at 12:26:58PM +0100, Andrz
https://bugzilla.kernel.org/show_bug.cgi?id=202061
Andrey Melentyev (andrey+ker...@psyduck.se) changed:
What|Removed |Added
CC||andrey+ker..
Hi, Christoph,
On Sat, 2019-01-05 at 09:01 +0100, Christoph Hellwig wrote:
> Hi Thomas,
>
> vmwgfx has been doing some odd checks based on DMA ops which rely
> on deep DMA mapping layer internals, and I think the changes in
> Linux 4.21 finally broke most of these implicit assumptions.
Thanks.
Reviewed-by: Thomas Hellstrom
On Sat, 2019-01-05 at 09:01 +0100, Christoph Hellwig wrote:
> intel_iommu_enabled is defined as always false for
> !CONFIG_INTEL_IOMMU,
> so remove the ifdefs around it.
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 18
On Tue, Jan 08, 2019 at 09:35:21AM +0100, Andrzej Hajda wrote:
> On 07.01.2019 22:56, Daniel Vetter wrote:
> > If you call drm_dev_register before you have all the components
> > assembled (i.e. anywhere else than in master bind) that sounds like a
> > driver bug.
>
>
> This is how components wor
https://bugzilla.kernel.org/show_bug.cgi?id=201867
--- Comment #2 from Andrey Melentyev (andrey+ker...@psyduck.se) ---
Possibly a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=200939 -
although that tickets lacks good description
--
You are receiving this mail because:
You are watchin
On Tue, Jan 08, 2019 at 10:22:06AM +0100, Andrzej Hajda wrote:
> What part of drm core disallows it? As I remember discussions about
> drm_bridge design there were voices that they should be
> hot(un)pluggable, and they are IMO, of course if they are not active.
Even if they are not active, once t
On Tue, Jan 8, 2019 at 10:22 AM Andrzej Hajda wrote:
>
> On 08.01.2019 09:47, Daniel Vetter wrote:
> > On Tue, Jan 8, 2019 at 9:35 AM Andrzej Hajda wrote:
> >> On 07.01.2019 22:56, Daniel Vetter wrote:
> >>> On Mon, Jan 7, 2019 at 5:27 PM Andrzej Hajda wrote:
> On 07.01.2019 17:08, Daniel V
On Tue, Jan 8, 2019 at 11:16 AM Russell King - ARM Linux
wrote:
>
> On Tue, Jan 08, 2019 at 09:35:21AM +0100, Andrzej Hajda wrote:
> > On 07.01.2019 22:56, Daniel Vetter wrote:
> > > If you call drm_dev_register before you have all the components
> > > assembled (i.e. anywhere else than in master
On 08.01.2019 11:23, Russell King - ARM Linux wrote:
> On Tue, Jan 08, 2019 at 10:22:06AM +0100, Andrzej Hajda wrote:
>> What part of drm core disallows it? As I remember discussions about
>> drm_bridge design there were voices that they should be
>> hot(un)pluggable, and they are IMO, of course if
On Wed, Jan 02, 2019 at 02:55:06PM -0300, Ezequiel Garcia wrote:
> The virtio_gpu_output is a member of struct virtio_gpu_device
> and is not a dynamically-allocated chunk, so it's wrong to kfree() it.
> Removing it fixes a memory corruption BUG() that can be triggered
> when the virtio-gpu driver
On Thu, Jan 03, 2019 at 01:16:00PM -0300, Ezequiel Garcia wrote:
> Move the code around so the driver is probed the bus
> .probe and removed from the bus .remove callbacks.
> This commit is just a cleanup and shouldn't affect
> functionality.
Doesn't apply cleanly to drm-misc-next, and git can't f
Hi,
On Sat, 2019-01-05 at 09:01 +0100, Christoph Hellwig wrote:
...
> intel_iommu_enabled is defined as always false for
> !CONFIG_INTEL_IOMMU,
> so remove the ifdefs around it.
>
> Signed-off-by: Christoph Hellwig
> ---
>
> -#if !defined(CONFIG_SWIOTLB) && !defined(CONFIG_INTEL_IOMMU)
> -
On Sat, 2019-01-05 at 09:01 +0100, Christoph Hellwig wrote:
> Just use a simple if/else chain to select the DMA mode.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Thomas Hellstrom
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 25 ++---
> 1 file changed, 6 insertions(
Conversion to atomic modesetting, step one.
Add atomic crtc helper callbacks.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/bochs/bochs_kms.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/gpu/drm/bochs/bochs_kms.c
b/drivers/gpu/drm/bochs/bochs_kms.c
i
Conversion to atomic modesetting, step two.
Add mode_set_nofb crtc helper callback.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_kms.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/bochs/bochs_kms.c
b/drivers/g
This series adds support for atomic modesetting to the bochs driver.
It also switches over to the generic fbdev implementation and does
some cleanups.
v2:
- some updates according to Oleksandr's review.
- fix ttm bo pin/unpin (new patch #15).
Gerd Hoffmann (15):
drm/bochs: encoder cleanup
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/bochs/bochs_drv.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/bochs/bochs_drv.c
b/drivers/gpu/drm/bochs/bochs_drv.c
index a9c7140e3b..350e34cf2c 100644
--- a/drivers/gpu/drm/bochs/bochs_drv.c
+++ b/d
bochs_fbdev.c is almost empty now. Move the remaining framebuffer bits
over to bochs_kms.c. Pure code motion. No functional change.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_fbdev.c | 29 -
drivers/gpu/drm/boc
Generic framebuffer emulation needs this.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs.h | 11 +++
drivers/gpu/drm/bochs/bochs_drv.c | 15 +-
drivers/gpu/drm/bochs/bochs_mm.c | 63 +++
3 fi
It's always NULL, so just remove it.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs.h | 2 +-
drivers/gpu/drm/bochs/bochs_fbdev.c | 2 +-
drivers/gpu/drm/bochs/bochs_kms.c | 2 +-
drivers/gpu/drm/bochs/bochs_mm.c| 11 +--
Conversion to atomic modesetting, step three.
Wire up atomic helpers. Switch planes to atomic.
We are late to the party, the transitional helpers are gone,
so this can't be splitted into smaller steps any more.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/
Conversion to atomic modesetting, step four.
Use atomic set_config helper for crtc.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_kms.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bochs/bochs_kms.c
b/dr
On 08.01.2019 11:24, Daniel Vetter wrote:
> On Tue, Jan 8, 2019 at 10:22 AM Andrzej Hajda wrote:
>> On 08.01.2019 09:47, Daniel Vetter wrote:
>>> On Tue, Jan 8, 2019 at 9:35 AM Andrzej Hajda wrote:
On 07.01.2019 22:56, Daniel Vetter wrote:
> On Mon, Jan 7, 2019 at 5:27 PM Andrzej Hajda
The buffer object must be reserved before calling
ttm_bo_validate for pinning/unpinning.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/bochs/bochs_mm.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/bochs/bochs_mm.c b/drivers/gpu/drm/bochs/bochs_mm.c
index cfe061c
Not needed any more, bochs uses the generic emulation now.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs.h | 9 ---
drivers/gpu/drm/bochs/bochs_drv.c | 6 --
drivers/gpu/drm/bochs/bochs_fbdev.c | 137 ---
Create a separate bochs_hw_setformat function to configure
the framebuffer format (actually just the byteorder).
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs.h | 5 +++--
drivers/gpu/drm/bochs/bochs_hw.c | 19 ---
driver
Remove the old, now unused crtc callbacks.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_kms.c | 81 ---
1 file changed, 81 deletions(-)
diff --git a/drivers/gpu/drm/bochs/bochs_kms.c
b/drivers/gpu/drm/boc
Most unused callbacks can be NULL pointers these days.
Drop a bunch of empty encoder callbacks.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_kms.c | 26 --
1 file changed, 26 deletions(-)
diff --git a/drivers/gpu/drm/
Conversion to atomic modesetting, step five.
Use atomic page_flip helper for crtc.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_kms.c | 23 +--
1 file changed, 1 insertion(+), 22 deletions(-)
diff --git a/drivers/gpu/drm/
Conversion to atomic modesetting, final step.
Set the DRIVER_ATOMIC flag.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/bochs/bochs_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bochs/bochs_drv.c
b/drivers/gpu/
https://bugzilla.kernel.org/show_bug.cgi?id=202061
--- Comment #2 from scafrogli...@gmail.com ---
In fact i have the same gpu
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.f
On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej Hajda wrote:
> Issues with device links have nothing to do with hotplugging, they are
> generic - lifetime of the objects (drm_bridge, drm_panel) is just
> slightly different of lifetime of device links, and this is racy even if
> you do not want ho
https://bugs.freedesktop.org/show_bug.cgi?id=109161
--- Comment #6 from Yanko Kaneti ---
FWIW I've been running linus rc1+ and after that 5.0.0-0.rc1.git0.1.fc30.x86_64
without having any issues with my Polaris11, where previously the bug triggered
in the first minute of use.
--
You are receivi
On 08.01.2019 12:38, Russell King - ARM Linux wrote:
> On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej Hajda wrote:
>> Issues with device links have nothing to do with hotplugging, they are
>> generic - lifetime of the objects (drm_bridge, drm_panel) is just
>> slightly different of lifetime of d
https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #4 from fin4...@hotmail.com ---
Use the DVI connector then. The HDMI development has a low priority. Developers
use the display port connector and it is computer oriented while HDMI is for
consumer electronics. I did sold my HDMI only
On Tue, Jan 08, 2019 at 09:51:45AM +, Thomas Hellstrom wrote:
> Hi, Christoph,
>
> On Sat, 2019-01-05 at 09:01 +0100, Christoph Hellwig wrote:
> > Hi Thomas,
> >
> > vmwgfx has been doing some odd checks based on DMA ops which rely
> > on deep DMA mapping layer internals, and I think the chan
On Tue, Jan 08, 2019 at 01:27:56PM +0100, Andrzej Hajda wrote:
> On 08.01.2019 12:38, Russell King - ARM Linux wrote:
> > On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej Hajda wrote:
> >> Issues with device links have nothing to do with hotplugging, they are
> >> generic - lifetime of the objects
https://bugs.freedesktop.org/show_bug.cgi?id=109217
--- Comment #2 from fin4...@hotmail.com ---
Created attachment 143009
--> https://bugs.freedesktop.org/attachment.cgi?id=143009&action=edit
5.0-rc1 dmesg
This bug is present in the 5.0-rc1 kernel too.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=109217
--- Comment #3 from fin4...@hotmail.com ---
Created attachment 143010
--> https://bugs.freedesktop.org/attachment.cgi?id=143010&action=edit
Xorg log
This bug is present in the 5.0-rc1 kernel too.
--
You are receiving this mail because:
You a
On Tue, Jan 8, 2019 at 2:22 PM Russell King - ARM Linux
wrote:
> On Tue, Jan 08, 2019 at 01:27:56PM +0100, Andrzej Hajda wrote:
> > On 08.01.2019 12:38, Russell King - ARM Linux wrote:
> > > On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej Hajda wrote:
> > >> Issues with device links have nothing
On Mon, Jan 7, 2019 at 11:36 AM Daniel Vetter wrote:
>
> On Wed, Jan 02, 2019 at 09:49:17AM +0100, Frank Wunderlich wrote:
> > From: CK Hu
> >
> > This patch adds Framebuffer-Driver for Mediatek
> >
> > currently tested on mt7623, maybe works on other platforms
> > MTK-FBDev written by CK Hu and
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #19 from Dan Horák ---
They (=
https://src.fedoraproject.org/fork/sharkcz/rpms/kernel/blob/talos/f/ppc64-talos-amdgpu-reset.patch)
can go upstream.
I have a 4.20 kernel on the host with recent firmware for polaris11, the
skiroot boo
https://bugs.freedesktop.org/show_bug.cgi?id=108464
--- Comment #16 from Harry Wentland ---
Created attachment 143011
--> https://bugs.freedesktop.org/attachment.cgi?id=143011&action=edit
[PATCH] drm/amd/display: Limit number of links to num_ddc
Can you see if this patch helps you?
--
You ar
On 1/8/19 3:37 AM, Daniel Vetter wrote:
> On Tue, Jan 08, 2019 at 11:12:41AM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the drm-misc tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In fun
Hi Uma,
On Thu, Dec 27, 2018 at 11:22:36PM +0530, Uma Shankar wrote:
> This patch series creates a new connector property to program
> colorspace to sink devices. Modern sink devices support more
> than 1 type of colorspace like 601, 709, BT2020 etc. This helps
> to switch based on content type wh
Hi Uma,
On Thu, Dec 27, 2018 at 11:22:37PM +0530, Uma Shankar wrote:
> This patch adds a colorspace connector property, enabling
> userspace to switch to various supported colorspaces.
> This will help enable BT2020 along with other colorspaces.
>
> v2: Addressed Maarten and Ville's review commen
https://bugs.freedesktop.org/show_bug.cgi?id=109246
--- Comment #5 from Alex Deucher ---
Do you have an option in your monitor's menu to poll inputs? If so can you
disable it? Some monitors poll inputs which sometimes causes the hpd pin to
fire which looks like a hotplug event to the driver.
-
On Tue, Jan 08, 2019 at 12:39:36AM +, Russell King - ARM Linux wrote:
> On Mon, Jan 07, 2019 at 10:55:15PM +0100, Daniel Vetter wrote:
> > On Mon, Jan 7, 2019 at 5:13 PM Russell King - ARM Linux
> > wrote:
> > >
> > > On Mon, Jan 07, 2019 at 11:45:32AM +0100, Daniel Vetter wrote:
> > > > On Th
On 08.01.2019 14:21, Russell King - ARM Linux wrote:
> On Tue, Jan 08, 2019 at 01:27:56PM +0100, Andrzej Hajda wrote:
>> On 08.01.2019 12:38, Russell King - ARM Linux wrote:
>>> On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej Hajda wrote:
Issues with device links have nothing to do with hotp
During an atomic commit, the HVS is configured with a display list
for the channel matching the associated CRTC. The Pixel Valve (CRTC)
and encoder are also configured for the new setup at that time.
While the Pixel Valve and encoder are reconfigured synchronously, the
HVS is only reconfigured afte
From: Boris Brezillon
The HVS block is supposed to fill the pixelvalve FIFOs fast enough to
meet the requested framerate. The problem is, the HVS and memory bus
bandwidths are limited, and if we don't take these limitations into
account we might end up with HVS underflow errors.
This patch is tr
In order to test whether the load tracker is working as expected, we
need the ability to compare the commit result with the underrun
indication. With the load tracker always enabled, commits that are
expected to trigger an underrun are always rejected, so userspace
cannot get the actual underrun in
From: Boris Brezillon
The DRM framework provides a generic way to report underrun errors.
Let's implement the necessary hooks to support it in the VC4 driver.
Signed-off-by: Boris Brezillon
---
Changes in v3:
- Generic underrun report function has been dropped, adjust the
code accordingly
Ch
Hi,
Here is a third iteration of the VC4 load tracking series, which was
initially developed by Boris Brezillon and that I have now taken over.
This new version aggregates a standalone patch adding a debugfs entry,
which was updated since its last revision. A new preliminary patch is
also introdu
On Tue, 2019-01-08 at 11:43 +0100, Gerd Hoffmann wrote:
> On Thu, Jan 03, 2019 at 01:16:00PM -0300, Ezequiel Garcia wrote:
> > Move the code around so the driver is probed the bus
> > .probe and removed from the bus .remove callbacks.
> > This commit is just a cleanup and shouldn't affect
> > funct
Move the code around so the driver is probed the bus
.probe and removed from the bus .remove callbacks.
This commit is just a cleanup and shouldn't affect
functionality.
Signed-off-by: Ezequiel Garcia
---
v2: rebased on drm-misc-next
drivers/gpu/drm/virtio/Makefile | 2 +-
drivers/gp
On Tue, Jan 08, 2019 at 03:33:54PM +0100, Andrzej Hajda wrote:
> On 08.01.2019 14:21, Russell King - ARM Linux wrote:
> > On Tue, Jan 08, 2019 at 01:27:56PM +0100, Andrzej Hajda wrote:
> >> On 08.01.2019 12:38, Russell King - ARM Linux wrote:
> >>> On Tue, Jan 08, 2019 at 12:25:34PM +0100, Andrzej
https://bugs.freedesktop.org/show_bug.cgi?id=109234
--- Comment #7 from bmil...@gmail.com ---
(In reply to fin4478 from comment #6)
> blablabla
This makes zero sense and is totally uncalled for, specially here. Go back to
posting your usual bs in Phoronix debianxfce, this is not the place. You ar
1 - 100 of 203 matches
Mail list logo
