From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Date: Thu, 16 Dec 2010 11:28:24 -0600 Message-ID: <4D0A4C38.3010105@freescale.com> References: <1279893639-24333-1-git-send-email-agust@denx.de> <1279893639-24333-6-git-send-email-agust@denx.de> <4D0A446E.5020600@freescale.com> 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: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org To: Grant Likely Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org, Anatolij Gustschin , devicetree-discuss@lists.ozlabs.org List-Id: devicetree@vger.kernel.org Grant Likely wrote: > No. It is a static property of the board/machine. It is expected it > to be encoded into the board's .dts file. Ok, but that only makes sense if the monitor is hard-wired to the board itself. If a user can attach any monitor he wants, then the EDID data can't be known at compile time. I guess it's no different than using hard-coded memory controller programming instead of SPD. You can safely avoid SPD only if the DDR chips are soldered on the board. It looks like I need to add board-specific EDID reading to the DIU driver. -- Timur Tabi Linux kernel developer at Freescale