On 7/20/25 17:45, Alex Deucher wrote:
DP (and all of its variants, eDP, USB-C thunderbolt) doesn't actually
use i2c directly. It's aux; you can do i2c over aux, but in the case
of MST, it's more like a network for displays so naively messing with
i2c buses from userspace won't do what you expec
On Sat, Jul 19, 2025 at 1:38 PM Felix Richter wrote:
>
> On 7/19/25 14:23, Mario Limonciello wrote:
> >
> > On 7/19/25 5:10 AM, Felix Richter wrote:
> >> Thanks for the reply.
> >>
> >> I am aware that i can read and `edid` via sysfs from the drm device.
> >> I did not know about `drm_info` but fr
On 7/19/25 12:02 PM, Felix Richter wrote:
On 7/19/25 14:23, Mario Limonciello wrote:
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device.
I did not know about `drm_info` but from a quick look at it I don't
thi
On 7/19/25 14:23, Mario Limonciello wrote:
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device.
I did not know about `drm_info` but from a quick look at it I don't
think it provides the information I need.
The p
On 7/19/25 5:10 AM, Felix Richter wrote:
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device. I
did not know about `drm_info` but from a quick look at it I don't think
it provides the information I need.
The problem is not that I need more information
Thanks for the reply.
I am aware that i can read and `edid` via sysfs from the drm device. I
did not know about `drm_info` but from a quick look at it I don't think
it provides the information I need.
The problem is not that I need more information about the attached
display. The problem is
On 7/17/2025 2:42 PM, Felix Richter wrote:
Hi,
just tested that this Bug still exists in kernel version 6.16-rc6. The
example trigger from my previous mail still works triggering screen
freezing shortly after invocation.
I also learned that setting kernel param `amdgpu.dcdebugmask=0x10` work
Hi,
just tested that this Bug still exists in kernel version 6.16-rc6. The
example trigger from my previous mail still works triggering screen
freezing shortly after invocation.
I also learned that setting kernel param `amdgpu.dcdebugmask=0x10` works
as a workaround.
Kind regards,
Felix Ri
