From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Seitz Subject: Re: LVDS Undetected Date: Wed, 11 May 2011 17:43:51 +0200 Message-ID: <4DCAAEB7.2010808@vtnd.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from srv6.berlinhosting.de (ns.km35939.keymachine.de [87.118.86.113]) by gabe.freedesktop.org (Postfix) with ESMTP id D1FEE9E75D for ; Wed, 11 May 2011 08:50:33 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org > 2) If there is a valid reason for 1, how can I force the output to be listed. Short answer: You can't. It is being discussed to implement kernel parameters to force a certain LVDS mode, abd there do exist some patches. But as much as I know there hasn't been a decision made if it even should be allowed to force LVDS on. For now, I'm really thinking about using a EDID hardware chip to tell the software what to do. Greets, Kiste