On Mon, Sep 3, 2018 at 8:12 PM, Mika Westerberg
wrote:
> We have seen one similar issue with LPSS devices when BIOS assigns
> device BARs above 4G (which is not the case here) and it turned out to
> be misconfigured MTRR register or something like that. It may not be
> related at all but it could
Scrambling is required for supporting any mode over 340MHz. If it's not
supported, reject any modes that would require it.
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nouveau_connector.c | 34 +++--
1 file changed, 22 insertions(+), 12 deletions(-)
diff --git
When SCDC is supported, make sure that we configure the GPU and monitor
to the same parameters.
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/dispnv50/disp.c | 40 -
1 file changed, 39 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nvkm/engine/disp/Kbuild| 1 +
.../gpu/drm/nouveau/nvkm/engine/disp/hdmigm200.c | 34 ++
drivers/gpu/drm/nouveau/nvkm/engine/disp/ior.h | 2 ++
.../gpu/drm/nouveau/nvkm/engine/disp/sorgm200.c| 1 +
The register programmed by the clock method needs to contain a different
setting for the link speed as well as special divider settings.
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nvkm/engine/disp/hdmigm200.c | 2 ++
drivers/gpu/drm/nouveau/nvkm/engine/disp/ior.h | 5 +
High pixel clocks are required to use a 40 TMDS divider instead of 10,
and even low ones may optionally use scrambling depending on device
support.
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/include/nvif/cl5070.h | 5 -
drivers/gpu/drm/nouveau/nvkm/engine/disp/ior.h
This is the beginnings of HDMI 2.0 support. All of the "extra"
features are left out, such as 12/16bpc, YUV420, etc.
I've verified that with this code, a GP108 (GT1030) can switch between
4k@60 and 1920x1080@60 on a LG 4K TV. Further, I've verified via i2c
tools, that the SCDC writes really do
https://bugs.freedesktop.org/show_bug.cgi?id=107818
Rhys Kidd changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=100228
Rhys Kidd changed:
What|Removed |Added
CC||no11...@gmail.com
--- Comment #21 from
https://bugs.freedesktop.org/show_bug.cgi?id=107818
--- Comment #3 from Boris Vinogradov ---
(In reply to Ilia Mirkin from comment #2)
> I think this is somewhat common in laptops. Not sure we have a solid theory
> on how to fix it though -- basically the GPU doesn't really come up as it
>
https://bugs.freedesktop.org/show_bug.cgi?id=107818
Ilia Mirkin changed:
What|Removed |Added
Summary|linux-4.18.5 every boot |[GP107] linux-4.18.5 every
https://bugs.freedesktop.org/show_bug.cgi?id=107818
--- Comment #1 from Boris Vinogradov ---
Created attachment 141431
--> https://bugs.freedesktop.org/attachment.cgi?id=141431=edit
Kernel log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107818
Bug ID: 107818
Summary: linux-4.18.5 every boot some drivers errors
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=107817
Bug ID: 107817
Summary: NV50 : Nvidia NVS295 - Printing out EDID errors about
not connected monitor ports
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=107447
--- Comment #6 from Takashi Iwai ---
Created attachment 141427
--> https://bugs.freedesktop.org/attachment.cgi?id=141427=edit
Test fix patch
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact
https://bugs.freedesktop.org/show_bug.cgi?id=107447
--- Comment #5 from Takashi Iwai ---
One problem seems to be that the thermal target is set only once by the linear
fallback, and forgotten. The patch below "fixes" that, at least, to keep
updating the fan with the linear fallback.
But,
On Mon, Sep 03, 2018 at 04:56:32PM +0800, Daniel Drake wrote:
> On Sat, Sep 1, 2018 at 3:12 AM, Bjorn Helgaas wrote:
> > If true, this sounds like some sort of erratum, so it would be good to
> > get some input from Intel, and I cc'd a few Intel folks.
>
> Yes, it would be great to get their
On Sat, Sep 1, 2018 at 3:12 AM, Bjorn Helgaas wrote:
> If true, this sounds like some sort of erratum, so it would be good to
> get some input from Intel, and I cc'd a few Intel folks.
Yes, it would be great to get their input.
> It's interesting that all the systems below are from Asus. That
https://bugs.freedesktop.org/show_bug.cgi?id=107504
--- Comment #1 from tianhang <1748215...@qq.com> ---
Xorg segmentation fault at RRProviderAutoConfigGpuScreen
this problem has also occured on on my machine with nvidia cards(GM204GL [Tesla
M60])
does the nouveau driver support this nvidia
19 matches
Mail list logo
