Had a meeting with Daniel and talked about bringing out generic
part of hyper-dmabuf to the userspace, which means we most likely
reuse IOCTLs defined in xen-zcopy for our use-case if we follow
his suggestion.
So assuming we use these IOCTLs as they are,
Several things I would like you to
On Tue, Apr 24, 2018 at 08:29:36PM +0300, Ville Syrjälä wrote:
> On Tue, Apr 24, 2018 at 04:22:42PM +0200, Daniel Vetter wrote:
> > Only used within drm.ko, no need to tempt drivers.
> >
> > Cc: Keith Packard
> > Cc: Ville Syrjala
> >
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #7 from dwagner ---
I cannot comment on how useful above patches are for the topic of this bug
report, but they are helpful for bug report
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--
You are
Allow userland to specify a syncobj that is waited on before a render job
starts processing.
v2: Use 0 as invalid syncobj to drop flag (Eric)
Drop extra newline (Eric)
Signed-off-by: Stefan Schake
---
drivers/gpu/drm/vc4/vc4_drv.h | 1 +
drivers/gpu/drm/vc4/vc4_gem.c |
https://bugs.freedesktop.org/show_bug.cgi?id=106222
--- Comment #1 from Ernst Sjöstrand ---
Created attachment 139065
--> https://bugs.freedesktop.org/attachment.cgi?id=139065=edit
xorg.log
--
You are receiving this mail because:
You are the assignee for the
On Tue, Apr 24, 2018 at 10:42:26AM -0700, Rodrigo Vivi wrote:
> On Mon, Apr 23, 2018 at 03:08:31PM -0700, matthew.s.atw...@intel.com wrote:
> > From: Matt Atwood
>
> Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
>
> (I'm adding this and
https://bugs.freedesktop.org/show_bug.cgi?id=103987
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi Tomi,
On Thursday, 5 April 2018 13:21:30 EEST Tomi Valkeinen wrote:
> On 04/04/18 17:23, Laurent Pinchart wrote:
> +WARN(out_width > dispc.feat->ovl_width_max,
> + "Requested OVL width (%d) is larger than can be supported
> (%d).\n",
> +
https://bugzilla.kernel.org/show_bug.cgi?id=199101
Kevin McCormack (harlemsquir...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
From: Matt Atwood
Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
v2: name change M -> ULX, add enumeration in KBL ULX
v3: add entry to IS_KABYLAKE
Signed-off-by: Matt Atwood
---
intel/intel_chipset.h | 6 --
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #49 from MirceaKitsune ---
Sorry about that: I posted my last message before reading your last one, and
didn't notice your mention about /var/log/messages being obsolete. Just
mentioning so you
On Tue, Apr 24, 2018 at 05:02:40PM -0400, Andrey Grodzovsky wrote:
>
>
> On 04/24/2018 03:44 PM, Daniel Vetter wrote:
> > On Tue, Apr 24, 2018 at 05:46:52PM +0200, Michel Dänzer wrote:
> > > Adding the dri-devel list, since this is driver independent code.
> > >
> > >
> > > On 2018-04-24 05:30
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #14 from Joel Sass ---
Sorry, I completely forgot that I was using a custom kernel. I downloaded it
from here:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries
and installed the .deb files directly.
On Fri, Apr 13, 2018 at 6:01 AM Daniel Vetter
wrote:
> This tries to align with the X.org communities's long-standing
> tradition of trying to be an inclusive community and handing out
> commit rights fairly freely.
> We also tend to not revoke commit rights for people
On Tue, Apr 24, 2018 at 4:28 PM, Harry Wentland wrote:
>
>
> On 2018-04-24 08:09 AM, Daniel Vetter wrote:
>> On Mon, Apr 23, 2018 at 02:19:44PM -0700, Manasi Navare wrote:
>>> On Mon, Apr 23, 2018 at 10:40:06AM -0400, Harry Wentland wrote:
On 2018-04-20 04:32 PM,
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #6 from Joel Sass ---
Will do! Sorry, I haven't had much time for testing recently.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--- Comment #22 from dwagner ---
Two patches posted by Harry Wentland in bug report
https://bugs.freedesktop.org/show_bug.cgi?id=106159
today may hold the key to get finally rid of this long-standing bug:
When I apply
https://bugs.freedesktop.org/show_bug.cgi?id=103277
dwagner changed:
What|Removed |Added
Status|NEEDINFO|REOPENED
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=106224
Bug ID: 106224
Summary: "Medieval 2 Total War" will sometimes crash system on
a R9 270 card
Product: Mesa
Version: 18.0
Hardware: x86-64 (AMD64)
OS: Linux
This doesn't require any additional functionality from the driver but
is a prerequisite to userland calling the syncobj ioctls.
Signed-off-by: Stefan Schake
---
drivers/gpu/drm/vc4/vc4_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Allow specifying a syncobj on render job submission where we store the
fence for the job. This gives userland flexible access to the fence.
v2: Use 0 as invalid syncobj to drop flag (Eric)
Don't reintroduce the padding (Eric)
Signed-off-by: Stefan Schake
---
v2 drops the extra syncobj parameter and gets rid of the submit flags
since 0 is never a valid syncobj handle.
This series allows userspace to submit syncobj handles for importing
a fence to wait on or exporting the job fence as part of submission.
The primary use of this is to enable native
On Wed, 2018-04-11 at 19:42 -0400, Lyude Paul wrote:
> Does what it says on the label, it's a little confusing debugging atomic
> check failures otherwise.
>
> Cc: Manasi Navare
> Cc: Ville Syrjälä
> Signed-off-by: Lyude Paul
On Tue, Apr 24, 2018 at 12:42:39PM -0700, matthew.s.atw...@intel.com wrote:
> From: Matt Atwood
>
> Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
>
> v2: name change M -> ULX, add enumeration in KBL ULX
> v3: add entry to IS_KABYLAKE
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #47 from i...@yahoo.com ---
(In reply to MirceaKitsune from comment #46)
> I found out what's causing the apitrace crash: It no longer happens when I
> use fresh settings, therefore something in my config was breaking it. Upon
>
https://bugs.freedesktop.org/show_bug.cgi?id=106193
--- Comment #4 from Joel Sass ---
Hey Harry,
Thanks for your help.
Should I be using my current kernel, or just download the newest source to
apply these patches against?
Some of the other patches didn't really have the
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--- Comment #23 from dwagner ---
(I should mention that a very long time ago, I also posted a bug report
specifically regarding the EDID-loading feature:
https://bugs.freedesktop.org/show_bug.cgi?id=102202)
--
You are
On 04/24/2018 05:21 PM, Eric W. Biederman wrote:
Andrey Grodzovsky writes:
On 04/24/2018 03:44 PM, Daniel Vetter wrote:
On Tue, Apr 24, 2018 at 05:46:52PM +0200, Michel Dänzer wrote:
Adding the dri-devel list, since this is driver independent code.
On
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #48 from MirceaKitsune ---
Created attachment 139071
--> https://bugs.freedesktop.org/attachment.cgi?id=139071=edit
/var/log/messages
I managed to trigger the GPU freeze while running Xonotic
On 04/24/2018 03:44 PM, Daniel Vetter wrote:
On Tue, Apr 24, 2018 at 05:46:52PM +0200, Michel Dänzer wrote:
Adding the dri-devel list, since this is driver independent code.
On 2018-04-24 05:30 PM, Andrey Grodzovsky wrote:
Avoid calling wait_event_killable when you are possibly being
On Friday, April 20, 2018 04:20:51 PM Geert Uytterhoeven wrote:
> Since commit a521422ea4ae6128 ("ARM: shmobile: mackerel: Remove Legacy C
> board code"), the only remaining platforms using this driver are SuperH
> SH-Mobile SoCs (sh7723). As both SUPERH and ARCH_SHMOBILE are set for
> these
https://bugzilla.kernel.org/show_bug.cgi?id=199101
c...@mailinator.com changed:
What|Removed |Added
CC||c...@mailinator.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Aaron Watry changed:
What|Removed |Added
Depends on||106209
Referenced
On Tue, Apr 24, 2018 at 3:34 AM, Stefan Schake wrote:
> On Tue, Apr 24, 2018 at 10:09 AM, Alexandru-Cosmin Gheorghe
> wrote:
>> On Mon, Apr 23, 2018 at 05:06:44PM -0700, John Stultz wrote:
>>> @@ -695,6 +704,15 @@ HWC2::Error
>>>
On Fri, Apr 20, 2018 at 05:21:11PM +0200, Daniel Vetter wrote:
> > At the very lowest level they will need to be handled differently for
> > many architectures, the questions is at what point we'll do the
> > branching out.
>
> Having at least struct page also in that list with (dma_addr_t,
https://bugs.freedesktop.org/show_bug.cgi?id=105284
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi Maxime and all,
I resend the e-mail since it was refused by some address(my phone
composed it in HTML). Sorry.
Il 24/04/2018 10:41, Maxime Ripard ha scritto:
Hi,
On Mon, Apr 23, 2018 at 04:37:33PM +0200, Giulio Benetti wrote:
Il 22/03/2018 19:05, Maxime Ripard ha scritto:
On Wed, Mar
Reviewed-by: Felix Kuehling
We could probably add a sanity check for n_devices to avoid user mode
causing excessive memory allocations in the kernel. There is no good
reason for this to be bigger than the number of GPUs in the system. The
maximum number of GPUs supported
Den 23.04.2018 18.16, skrev Tom Callaway:
The PiTFT (ili9340) has a hardware reset circuit that resets only
on power-on and not on each reboot through a gpio like the
rpi-display does. As a result, we need to always apply the
rotation value regardless of the display "on/off" state.
Moved the
Maxime Ripard writes:
> The vc4 HVS uses an internal RGB888 representation of the frames, and will
> by default expand formats using a lower depth using zeros.
>
> This causes an issue when we try to use other compositing software such as
> pixman that seems to be
On Tue, Apr 24, 2018 at 7:30 PM, Emil Velikov wrote:
> On 13 April 2018 at 11:00, Daniel Vetter wrote:
>> This tries to align with the X.org communities's long-standing
>> tradition of trying to be an inclusive community and handing out
>> commit
On Tue, Apr 24, 2018 at 06:51:07PM +0300, Jyri Sarha wrote:
> Remove all drm_panel_detach() calls from all panel drives update the
> kernel doc for drm_panel_detach().
>
> Setting the connector and drm to NULL when the drm panel device is
> going away hardly serves any purpose. Usually the the
On Thu, Apr 19, 2018 at 05:32:23PM +0800, Chen-Yu Tsai wrote:
> This panel is marketed as Banana Pi 7" LCD display. On the back is
> a sticker denoting the model name S070WV20-CT16.
>
> This is a 7" 800x480 panel connected through a 24-bit RGB interface.
> However the panel only does 262k colors.
From: Matt Atwood
v2: name change M -> ULX, add enumeration in KBL ULX
Signed-off-by: Matt Atwood
---
intel/intel_chipset.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/intel/intel_chipset.h
https://bugs.freedesktop.org/show_bug.cgi?id=102820
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
On 2018-04-24 09:14 AM, Luc Van Oostenryck wrote:
> The method (*hqd_destroy) is defined as using an 'uint32_t'
> as 3rd argument but the the actual implementation of this
> method and all its calls actually uses an 'enum kfd_preempt_type'
> for this argument.
>
> Fix this by using 'enum
Den 24.04.2018 21.16, skrev Daniel Vetter:
On Tue, Apr 24, 2018 at 6:52 PM, Noralf Trønnes wrote:
Den 23.04.2018 18.16, skrev Tom Callaway:
The PiTFT (ili9340) has a hardware reset circuit that resets only
on power-on and not on each reboot through a gpio like the
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #4 from Harry Wentland ---
Created attachment 139069
--> https://bugs.freedesktop.org/attachment.cgi?id=139069=edit
[PATCH 1/2] drm/amd/display: Update MST edid property every time
--
You are receiving
On Tue, Apr 24, 2018 at 05:46:52PM +0200, Michel Dänzer wrote:
>
> Adding the dri-devel list, since this is driver independent code.
>
>
> On 2018-04-24 05:30 PM, Andrey Grodzovsky wrote:
> > Avoid calling wait_event_killable when you are possibly being called
> > from get_signal routine since
On 24/04/18 13:14, Peter Rosin wrote:
> On 2018-04-24 10:08, Russell King - ARM Linux wrote:
>> On Tue, Apr 24, 2018 at 08:58:42AM +0200, Peter Rosin wrote:
>>> On 2018-04-23 18:08, Russell King - ARM Linux wrote:
On Mon, Apr 23, 2018 at 09:23:00AM +0200, Peter Rosin wrote:
> static int
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #8 from Mariusz Ceier ---
I had these patches in the kernel tree - mine is from 22nd April, while these
patches were committed on 12th April.
Hi Maxime, Il 24 apr 2018 10:41, Maxime Ripard ha scritto:Hi,
On Mon, Apr 23, 2018 at 04:37:33PM +0200, Giulio Benetti wrote:
> Il 22/03/2018 19:05, Maxime Ripard ha scritto:
> > On Wed, Mar 21, 2018 at 09:03:13PM +0100, Giulio Benetti wrote:
> > > The
On Mon, Apr 09, 2018 at 11:14:17AM +0200, Daniel Vetter wrote:
> On Fri, Apr 06, 2018 at 04:56:48PM -0700, Keith Packard wrote:
> > (This is an RFC on whether this pair of ioctls seems reasonable. The
> > code compiles, but I haven't tested it as I'm away from home this
> > weekend.)
> >
> > I'm
Malidp uses two interrupts ie 1. se_irq - used for memory writeback.
and 2. de_irq - used for display output.
Extract the hardware initialization part from malidp interrupt registration
ie (malidp_de_irq_init()/ malidp_se_irq_init()) into a separate function
(ie
Malidp uses two interrupts ie 1. se_irq - used for memory writeback.
and 2. de_irq - used for display output.
'struct drm_device' is being replaced with 'struct malidp_hw_device'
as the function argument. The reason being the dependency of
malidp_de_irq_fini on 'struct drm_device' needs to be
Display and scaling engine interrupts need to be disabled when the
runtime pm invokes malidp_runtime_pm_suspend(). Conversely, they
need to be enabled in malidp_runtime_pm_resume().
This patch depends on:
https://lkml.org/lkml/2017/5/15/695
Signed-off-by: Ayan Kumar Halder
One needs to store the value of the OUTPUT_DEPTH that one has parsed from
device tree, so that it can be restored on system resume. This value is
set in the modeset function as this gets reset when the system suspends.
Signed-off-by: Ayan Kumar Halder
---
Changes in v3:-
-
malidp_pm_suspend_late checks if the runtime status is not suspended
and if so, invokes malidp_runtime_pm_suspend which disables the
display engine/core interrupts and the clocks. It sets the runtime status
as suspended.
The difference between suspend() and suspend_late() is as follows:-
1.
This patch series enhances and fixes certain issues relevant to system and
runtime power management on malidp.
---
Changes in v3:
- Squashed some commits.
- Fixed an issue related to writeback.
Reported-by: Alexandru-Cosmin Gheorghe
Changes in v2:
- Removed
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #45 from MirceaKitsune ---
(In reply to iive from comment #44)
I'm doing my best to debug this as well as possible, but there are a lot of
points and it's hard to pay attention to everything. I
https://bugs.freedesktop.org/show_bug.cgi?id=104319
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=101900
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
On Tue, Apr 24, 2018 at 6:52 PM, Noralf Trønnes wrote:
>
> Den 23.04.2018 18.16, skrev Tom Callaway:
>>
>> The PiTFT (ili9340) has a hardware reset circuit that resets only
>> on power-on and not on each reboot through a gpio like the
>> rpi-display does. As a result, we need
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #46 from MirceaKitsune ---
I found out what's causing the apitrace crash: It no longer happens when I use
fresh settings, therefore something in my config was breaking it. Upon further
On Tue, Apr 24, 2018 at 05:26:30PM +0300, Ville Syrjälä wrote:
> On Tue, Apr 24, 2018 at 04:18:37PM +0200, Daniel Vetter wrote:
> > On Tue, Apr 24, 2018 at 04:02:50PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > We're currently failing to reset
https://bugs.freedesktop.org/show_bug.cgi?id=106222
Bug ID: 106222
Summary: kernel BUG at __slab_free from dc_sink_release
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #44 from i...@yahoo.com ---
You haven't looked for the kernel panic message in the logs.
I'm still waiting for it.
As for the trace. I did download and traced Xonotic before writing the
instructions. I had no issues using the EXACT
On Thu, Apr 19, 2018 at 11:31:03AM +0200, Jacopo Mondi wrote:
> The THC63LVD1024 LVDS to RGB bridge supports two different input mapping
> modes, selectable by means of an external pin.
>
> Describe the LVDS mode map through a newly defined mandatory property in
> device tree bindings.
>
>
On Tue, Apr 24, 2018 at 04:22:42PM +0200, Daniel Vetter wrote:
> Only used within drm.ko, no need to tempt drivers.
>
> Cc: Keith Packard
> Cc: Ville Syrjala
> Signed-off-by: Daniel Vetter
Reviewed-by: Ville Syrjälä
https://bugs.freedesktop.org/show_bug.cgi?id=106222
--- Comment #2 from Ernst Sjöstrand ---
My screens always act a bit weird when waking up, they often blink very many
times and jump around a bit and give warnings in the logs etc. The Windows
driver also shows warnings every
https://bugs.freedesktop.org/show_bug.cgi?id=104281
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--- Comment #18 from David Henningsson ---
(In reply to Michel Dänzer from comment #10)
> (In reply to David Henningsson from comment #8)
> > The regression is between 4.15rc2 and 4.15rc3
>
> Any chance you can bisect between
From: Matt Atwood
Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
v2: name change M -> ULX, add enumeration in KBL ULX
Signed-off-by: Matt Atwood
---
intel/intel_chipset.h | 3 ++-
1 file changed, 2
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #9 from tempel.jul...@gmail.com ---
I got them too. Before those commits, my issue was way more severe. It's still
really nasty stutter though.
--
You are receiving this mail because:
You are the assignee for the
On Mon, Apr 23, 2018 at 03:08:31PM -0700, matthew.s.atw...@intel.com wrote:
> From: Matt Atwood
Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
(I'm adding this and pushing. Thanks for the patch)
>
> Signed-off-by: Matt Atwood
On Tue, Apr 24, 2018 at 10:55:05AM -0700, matthew.s.atw...@intel.com wrote:
> From: Matt Atwood
please add the message:
Based on kernel commit '672e314b21dc ("drm/i915/kbl: Add KBL GT2 sku")'
>
> v2: name change M -> ULX, add enumeration in KBL ULX
>
>
On 24/04/18 20:06, Russell King - ARM Linux wrote:
> On Tue, Apr 24, 2018 at 07:04:16PM +0300, Jyri Sarha wrote:
>> On 24/04/18 13:14, Peter Rosin wrote:
>>> On 2018-04-24 10:08, Russell King - ARM Linux wrote:
On Tue, Apr 24, 2018 at 08:58:42AM +0200, Peter Rosin wrote:
> On 2018-04-23
On 13 April 2018 at 11:00, Daniel Vetter wrote:
> This tries to align with the X.org communities's long-standing
> tradition of trying to be an inclusive community and handing out
> commit rights fairly freely.
>
> We also tend to not revoke commit rights for people no
https://bugs.freedesktop.org/show_bug.cgi?id=106006
--- Comment #13 from Harry Wentland ---
Not sure exactly how that kernel is assembled but it contains the problematic
code in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_color.c. You should be
able to simply delete
https://bugzilla.kernel.org/show_bug.cgi?id=199101
--- Comment #24 from Harry Wentland (harry.wentl...@amd.com) ---
Kevin, can you mark this as resolved?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=199101
--- Comment #25 from Thomas Crider (tcride...@gmail.com) ---
I can also confirm the flicker is gone with 4.17rc2
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
On Tue, Apr 24, 2018 at 8:48 PM, Christoph Hellwig wrote:
> On Fri, Apr 20, 2018 at 05:21:11PM +0200, Daniel Vetter wrote:
>> > At the very lowest level they will need to be handled differently for
>> > many architectures, the questions is at what point we'll do the
>> >
https://bugs.freedesktop.org/show_bug.cgi?id=106159
--- Comment #5 from Harry Wentland ---
Created attachment 139070
--> https://bugs.freedesktop.org/attachment.cgi?id=139070=edit
[PATCH 2/2] drm/amd/display: Check dc_sink every time in MST hotplug
Can you try patches
Hi Julia,
Thank you for the patch.
On Tuesday, 10 April 2018 08:49:40 EEST Julia Lawall wrote:
> From: Fengguang Wu
>
> PTR_ERR should normally access the value just tested by IS_ERR
>
> Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
>
> Fixes: 742243a44a73
https://bugs.freedesktop.org/show_bug.cgi?id=106225
Bug ID: 106225
Summary: Kernel panic after modesetting (not on every boot) on
ryzen 5 2400g
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS:
Hi Kieran,
I love your patch! Yet something to improve:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.17-rc2 next-20180424]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
https://bugs.freedesktop.org/show_bug.cgi?id=106191
--- Comment #12 from François Jacques ---
Created attachment 139082
--> https://bugs.freedesktop.org/attachment.cgi?id=139082=edit
dmesg (Linux 4.16.3, drm.debug=0x06, audio enabled)
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=106191
--- Comment #13 from François Jacques ---
Created attachment 139083
--> https://bugs.freedesktop.org/attachment.cgi?id=139083=edit
REAL dmesg output (with debug messages)
Last attachment for tonight. This one its
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-4.15
head: 9556f93f18f7923978fb90f860c107fed9ca7f57
commit: 54df8c4830456ee6d9f9cb16c281e8bef8780dce [1429/1759] drm/amd/dkms: add
amdkfd module
config: x86_64-federa-25 (attached as .config)
compiler: gcc-7 (Debian
https://bugs.freedesktop.org/show_bug.cgi?id=106228
Bug ID: 106228
Summary: amdgpu reads back brightness 0 (which is not true) if
checked before a brightness has been explicitly set
Product: DRI
Version: unspecified
https://bugs.freedesktop.org/show_bug.cgi?id=106229
--- Comment #1 from Alex Deucher ---
Does it work on x86?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=106229
--- Comment #2 from Luke-Jr ---
Never tried amdgpu on x86.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Tue, Apr 24, 2018 at 7:31 AM, Ezequiel Garcia
wrote:
> Hi Doug, Sean:
>
> I would like to move this forward.
>
> On 26 February 2018 at 15:23, Doug Anderson wrote:
>> Hi,
>>
>> On Thu, Feb 8, 2018 at 9:48 AM, Sean Paul
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-4.15
head: 9556f93f18f7923978fb90f860c107fed9ca7f57
commit: 02349fbb559640a1f948df9c84e8f65bd2565d57 [1098/1759] drm/amdkcl: [4.11]
fix debugfs func
coccinelle warnings: (new ones prefixed by >>)
>>
https://bugs.freedesktop.org/show_bug.cgi?id=106229
Bug ID: 106229
Summary: EEH problem at boot with Radeon HD 7950, in
amdgpu_mm_rreg
Product: DRI
Version: XOrg git
Hardware: PowerPC
OS: Linux (All)
On Wed, 2018-04-11 at 18:54 -0400, Lyude Paul wrote:
> While having the modeset_retry_work in intel_connector makes sense with
> SST, this paradigm doesn't make a whole ton of sense when it comes to
> MST since we have to deal with multiple connectors. In most cases, it's
> more useful to just
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #10 from Mike Bendel ---
I have the same issue. For me amdgpu.dc=0 does not really fix it either. I have
a 3840x1600 monitor running at 75 Hz. This is the different behavior I noticed
when toggling the DC setting:
Hi,
On Tue, Apr 24, 2018 at 7:31 AM, Ezequiel Garcia
wrote:
> Hi Doug, Sean:
>
> I would like to move this forward.
>
> On 26 February 2018 at 15:23, Doug Anderson wrote:
>> Hi,
>>
>> On Thu, Feb 8, 2018 at 9:48 AM, Sean Paul
Fixes: 61986dd6bef0 ("drm/amdkfd: Copy in KFD-related files")
Signed-off-by: Fengguang Wu
---
amdgpu_amdkfd_fence.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-4.15
head: 9556f93f18f7923978fb90f860c107fed9ca7f57
commit: 61986dd6bef0b17e85a9846bb4d1ca610f9d6ce0 [1409/1759] drm/amdkfd: Copy
in KFD-related files
config: i386-randconfig-a1-04241604 (attached as .config)
compiler:
1 - 100 of 272 matches
Mail list logo