linux-kernel - Re: [RFC PATCH 3/5] drm/i915: register LVDS connector even if we can't get a panel mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120805211412.GG12232@phenom.ffwll.local>
Date:	Sun, 5 Aug 2012 23:14:12 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Matthew Garrett <mjg59@...f.ucam.org>,
	dri-devel@...ts.freedesktop.org,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	Andreas Heider <andreas@...tr.de>
Subject: Re: [RFC PATCH 3/5] drm/i915: register LVDS connector even if we
 can't get a panel mode

On Sat, Aug 04, 2012 at 11:57:27AM -0500, Seth Forshee wrote:
> On Fri, Aug 03, 2012 at 05:27:02PM +0100, Matthew Garrett wrote:
> > On Fri, Aug 03, 2012 at 11:24:51AM -0500, Seth Forshee wrote:
> > 
> > > This is one of the things I wasn't so sure about. There are various
> > > checks in intel_lvds_init() that can cause it to bail out before we try
> > > to get the EDID, and I don't fully understand all of them. If non-laptop
> > > machines are expected to bail out before the EDID check then the
> > > approach I've taken seems reasonable. Otherwise adding a quirk probably
> > > is a good idea.
> > 
> > I know we've previously had problems with machines with phantom LVDS 
> > hardware, but I'm not sure what the current state of affairs is.
> 
> It turns out that the framebuffer console issue is due to not having a
> mode when initializing LVDS. As a result 1024x768 is getting used for
> the framebuffer.
> 
> So quirking is going to fix this situation. In fact, with the changes
> below switcheroo seems to work perfectly, without any of these patches
> at all.

I like this approach more - the only other solution I see is to ask the
currently active driver (i.e. radeon) at bootime for the right mode. Which
sounds much more hellish and fragile ...
-Daniel
-- 
Daniel Vetter
Mail: daniel@...ll.ch
Mobile: +41 (0)79 365 57 48
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/