From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
Subject: [Bug 47846] Nouveau -> overscan using HDMI
Date: Fri, 13 Apr 2012 06:44:00 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Errors-To: nouveau-bounces+gcfxn-nouveau=m.gmane.org-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
List-Id: nouveau.vger.kernel.org
https://bugs.freedesktop.org/show_bug.cgi?id=47846
--- Comment #5 from lameventanas-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 2012-04-12 23:44:00 PDT ---
After playing with xrandr and this new underscan parameter I have concluded
this is just an ugly workaround that doesn't fix the root problem which is
getting EDID right.
Everything still looks wrong, I think the problem is that by using this
underscan thing the applications still think the resolution is 1366x768 when
its no longer the case.
And of course there is also the overscan at boot time problem.
So is there any way to fix the way nouveau interprets the EDID data to make it
work like nvidia's driver?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.