From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [PATCH 1/3] drivers-gpu-drm-allow-to-load-edid-firmware.patch Date: Sun, 11 Mar 2012 13:44:05 +0000 Message-ID: <20120311134405.05942964@pyramind.ukuu.org.uk> References: <20120310202014.828058552@osadl.org> <20120310202241.764367925@osadl.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from lxorguk.ukuu.org.uk (lxorguk.ukuu.org.uk [81.2.110.251]) by gabe.freedesktop.org (Postfix) with ESMTP id 3935E9E9B7 for ; Sun, 11 Mar 2012 06:42:10 -0700 (PDT) In-Reply-To: <20120310202241.764367925@osadl.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Carsten Emde Cc: Thomas Gleixner , LKML , DRI List-Id: dri-devel@lists.freedesktop.org > This patch allows to load an EDID data set via the firmware interface. > It contains data sets of frequently used screen resolutions (1024x768, > 1280x1024, 1680x1050 and 1920x1080). The requested EDID data are > specified as a module parameter of the drm_kms_helper module, e.g. > options drm_kms_helper edid_firmware=edid/1280x1024.bin or as kernel > command line parameter. What if the DRM layer and driver are compiled in. They'll come up as console before the file system so the firmware request will hang ? Given the EDID is tiny and is data not code wouldn't it be simpler (and smaller) if this option compiled in a few generic EDIDs to use ? Alan