-Original Message-
From: Thomas Zimmermann [mailto:tzimmerm...@suse.de]
Sent: Tuesday, August 03, 2021 4:58 PM
To: Kuo-Hsiang Chou ;
dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org
Subject: Re: [PATCH v5] drm/ast: Fixed CVE for DP501
Hi
Am 29.04.21 um 11:21 schrieb Kuo
Hi
Am 29.04.21 um 11:21 schrieb Kuo-Hsiang Chou:
More generally speaking, the DP501 code needs a major refactoring. It's
currently bolted onto the regular VGA connector code. It should rather be a
separate connector or a DRM bridge. I always wanted to work on this, but don't
have a device
-Original Message-
From: Thomas Zimmermann [mailto:tzimmerm...@suse.de]
Sent: Tuesday, April 27, 2021 7:02 PM
To: Kuo-Hsiang Chou ;
dri-devel@lists.freedesktop.org; linux-ker...@vger.kernel.org
Subject: Re: [PATCH v5] drm/ast: Fixed CVE for DP501
Hi Thomas,
Hi
Am 21.04.21 um 10:58
Hi
Am 21.04.21 um 10:58 schrieb KuoHsiang Chou:
[Bug][DP501]
If ASPEED P2A (PCI to AHB) bridge is disabled and disallowed for
CVE_2019_6260 item3, and then the monitor's EDID is unable read through
Parade DP501.
The reason is the DP501's FW is mapped to BMC addressing space rather
than Host
[Bug][DP501]
If ASPEED P2A (PCI to AHB) bridge is disabled and disallowed for
CVE_2019_6260 item3, and then the monitor's EDID is unable read through
Parade DP501.
The reason is the DP501's FW is mapped to BMC addressing space rather
than Host addressing space.
The resolution is that using
