Using strncpy() does not always terminate the destination string.
stracpy() is a alternative function that does, by using this new
function we will no longer need to insert a null separator.
Signed-off-by: Adam Zerella
---
drivers/staging/android/ion/ion.c | 3 +--
1 file changed, 1
https://bugs.freedesktop.org/show_bug.cgi?id=111555
--- Comment #4 from Shmerl ---
(In reply to Andrew Sheldon from comment #3)
> Are you running a monitor at 75hz?
>
No, 60 Hz which is my monitor's native refresh rate.
--
You are receiving this mail because:
You are the assignee for the
drm_gem_reservation_object_wait() returns 0 if it succeeds and -ETIME
if it timeouts, but lima driver assumed that 0 is error.
Cc: sta...@vger.kernel.org
Signed-off-by: Vasily Khoruzhick
---
drivers/gpu/drm/lima/lima_gem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=111555
--- Comment #3 from Andrew Sheldon ---
Are you running a monitor at 75hz?
I can only trigger the bug when setting 74-76hz with amd-staging-drm-next, and
although I haven't tested in a while, I suspect the same applies with 5.3-rcX
(and
https://bugs.freedesktop.org/show_bug.cgi?id=111232
--- Comment #5 from bibitocarlos ---
Seems to be related to this bug:
https://lore.kernel.org/lkml/624bfb8f-b586-492e-ea6-4b138daec...@canonical.com/T/
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111482
--- Comment #16 from Andrew Sheldon ---
One possibility could be to create a custom modeline, perhaps trying refresh
rates between 30-60hz (starting with 45hz), so you can find a point where the
high idle power usage kicks in. Reduced blanking
https://bugs.freedesktop.org/show_bug.cgi?id=111232
--- Comment #4 from bibitocarlos ---
I have finished bisecting.
This is the commit which created the bug :
" Bissection : 0 révision à tester après ceci (à peu près 0 étape)
[005440066f929ba0dca8f4e0aebfbf8daac592cc] drm/amdgpu: enable gfxoff
On Wed, Aug 21, 2019 at 7:55 AM Thierry Reding wrote:
>
> On Wed, Aug 21, 2019 at 04:33:58PM +1000, Ben Skeggs wrote:
> > On Wed, 14 Aug 2019 at 20:14, Gerd Hoffmann wrote:
> > >
> > > Hi,
> > >
> > > > > Changing the order doesn't look hard. Patch attached (untested, have
> > > > > no
> > >
On Sat, Sep 7, 2019 at 7:20 PM Mun, Gwan-gyeong
wrote:
>
> On Fri, 2019-09-06 at 09:24 -0400, Ilia Mirkin wrote:
> > On Fri, Sep 6, 2019 at 7:43 AM Ville Syrjälä
> > wrote:
> > > On Fri, Sep 06, 2019 at 11:31:55AM +, Shankar, Uma wrote:
> > > >
> > > > > -Original Message-
> > > > >
On Fri, 2019-09-06 at 09:24 -0400, Ilia Mirkin wrote:
> On Fri, Sep 6, 2019 at 7:43 AM Ville Syrjälä
> wrote:
> > On Fri, Sep 06, 2019 at 11:31:55AM +, Shankar, Uma wrote:
> > >
> > > > -Original Message-
> > > > From: Ilia Mirkin
> > > > Sent: Tuesday, September 3, 2019 6:12 PM
> >
Support for HDR10 video was introduced in DisplayPort 1.4.
On GLK+ platform, in order to use DisplayPort HDR10, we need to support
BT.2020 colorimetry and HDR Static metadata.
It implements the CTA-861-G standard for transport of static HDR metadata.
It enables writing of HDR metadata infoframe
According to Bspec, GEN11 and prior GEN11 have different register size for
HDR Metadata Infoframe SDP packet. It adds new VIDEO_DIP_GMP_DATA_SIZE for
GEN11. And it makes handle different register size for
HDMI_PACKET_TYPE_GAMUT_METADATA on hsw_dip_data_size() for each GEN
platforms. It addresses
It attaches the colorspace connector property to a DisplayPort connector.
Based on colorspace change, modeset will be triggered to switch to a new
colorspace.
Based on colorspace property value create a VSC SDP packet with appropriate
colorspace. This would help to enable wider color gamut like
When BT.2020 Colorimetry output is used for DP, we should program BT.2020
Colorimetry to MSA and VSC SDP. It adds output_colorspace to
intel_crtc_state struct as a place holder of pipe's output colorspace.
In order to distinguish needed colorimetry for VSC SDP, it adds
intel_dp_needs_vsc_sdp
It refactors and renames a function which handled vsc sdp header and data
block setup for supporting colorimetry format.
Function intel_dp_setup_vsc_sdp handles vsc sdp header and data block
setup for pixel encoding / colorimetry format.
In order to use colorspace information of a connector, it
In order to use colorspace property to Display Port connectors, it extends
DRM_MODE_CONNECTOR_DisplayPort connector_type on
drm_mode_create_colorspace_property function.
v3: Addressed review comments from Ville
- Add new colorimetry options for DP 1.4a spec.
- Separate set of colorimetry
It attaches HDR metadata property to DP connector on GLK+.
It enables HDR metadata infoframe sdp on GLK+ to be used to send
HDR metadata to DP sink.
v2: Minor style fix
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_dp.c | 5 +
1 file
Function intel_dp_setup_hdr_metadata_infoframe_sdp handles Infoframe SDP
header and data block setup for HDR Static Metadata. It enables writing of
HDR metadata infoframe SDP to panel. Support for HDR video was introduced
in DisplayPort 1.4. It implements the CTA-861-G standard for transport of
Bail from the pci_driver probe function instead of from the drm_driver
load function.
This avoid /dev/dri/card0 temporarily getting registered and then
unregistered again, sending unwanted add / remove udev events to
userspace.
Specifically this avoids triggering the (userspace) bug fixed by
On Sat, Sep 7, 2019 at 3:18 AM Rob Clark wrote:
>
> On Fri, Sep 6, 2019 at 3:16 PM Marek Olšák wrote:
> >
> > + dri-devel
> >
> > On Tue, Sep 3, 2019 at 5:41 PM Jiang, Sonny wrote:
> >>
> >> Add DRM device name and use DRM_IOCTL_VERSION ioctl drmVersion::desc
> >> passing it to user space
> >>
On Fri, Sep 6, 2019 at 2:42 PM Steven Price wrote:
>
> On 06/09/2019 12:10, Rob Herring wrote:
> > On Thu, Sep 5, 2019 at 1:11 PM Steven Price wrote:
> >>
> >> When handling a GPU page fault addr_to_drm_mm_node() is used to
> >> translate the GPU address to a buffer object. However it is
https://bugs.freedesktop.org/show_bug.cgi?id=111077
--- Comment #27 from Matt Turner ---
Is the shader-cache causing the shaders to be loaded from disk instead of
compiled?
Try with the environment variable MESA_GLSL_CACHE_DISABLE=1
--
You are receiving this mail because:
You are the assignee
On Wed, 2019-09-04 at 08:08 -0400, Sasha Levin wrote:
> it's better to get
> it right rather than to be done quickly :)
That also applies to the initial selection of
patches for the stable trees.
___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=111584
Bug ID: 111584
Summary: "pp_od_clk_voltage" unavailable on Hawaii GPU (R9 390)
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Tue, Sep 3, 2019 at 4:16 PM Daniel Vetter wrote:
>
> On Tue, Sep 3, 2019 at 10:01 PM Sasha Levin wrote:
> >
> > On Tue, Sep 03, 2019 at 07:03:47PM +0200, Greg KH wrote:
> > >On Tue, Sep 03, 2019 at 06:40:43PM +0200, Michel Dänzer wrote:
> > >> On 2019-09-03 6:23 p.m., Sasha Levin wrote:
> >
https://bugzilla.kernel.org/show_bug.cgi?id=204683
--- Comment #8 from Matthias Heinz (m...@familie-heinz.name) ---
I was wrong. 2c3cd66f4c66, which is the predecessor of 634092b1b9f6 just
crashed on me. Well, back to the drawing board... (eh, bisecting)
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=111527
tele4...@hotmail.com changed:
What|Removed |Added
CC||tele4...@hotmail.com
--- Comment
On Sat, Sep 7, 2019 at 11:05 AM Alexander Kapshuk
wrote:
>
> To Whom It May Concern
>
> Every kernel I have built since 5.3.0-rc2-next-20190730 and up to
> 5.3.0-rc7-next-20190903 has resulted in the kernel panic described below.
>
> The panic occurs early on in the boot process, so no records of
To Whom It May Concern
Every kernel I have built since 5.3.0-rc2-next-20190730 and up to
5.3.0-rc7-next-20190903 has resulted in the kernel panic described below.
The panic occurs early on in the boot process, so no records of it get
written on disk. I resourted to taking photos and videos to
On Fri, Sep 06, 2019 at 07:47:30PM +0200, Daniel Vetter wrote:
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index 5a03417e5bf7..4edd98b06834 100644
> +++ b/include/linux/mmu_notifier.h
> @@ -356,13 +356,14 @@ mmu_notifier_invalidate_range_start(struct
>
On Sat, 2019-09-07 at 00:21 -0700, Dhinakaran Pandiyan wrote:
> Gen-12 has a new compression format, add a new modifier to indicate that.
>
> Cc: Ville Syrjälä
> Cc: Matt Roper
> Cc: Nanley G Chery
> Cc: Jason Ekstrand
Cc: dri-devel@lists.freedesktop.org
> Signed-off-by: Dhinakaran Pandiyan
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #11 from Christopher Snowhill (kod...@gmail.com) ---
Oops, I neglected to mention: The system is non-responsive to input devices, as
the USB input appears to all be completely powered off after the GPU crashes,
but the network
https://bugzilla.kernel.org/show_bug.cgi?id=204559
Christopher Snowhill (kod...@gmail.com) changed:
What|Removed |Added
CC|
33 matches
Mail list logo
