From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Date: Thu, 16 Dec 2010 10:42:21 -0700 Message-ID: References: <1279893639-24333-1-git-send-email-agust@denx.de> <1279893639-24333-6-git-send-email-agust@denx.de> <4D0A446E.5020600@freescale.com> <4D0A4C38.3010105@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4D0A4C38.3010105@freescale.com> 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: Timur Tabi Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org, Anatolij Gustschin , devicetree-discuss@lists.ozlabs.org List-Id: devicetree@vger.kernel.org On Thu, Dec 16, 2010 at 10:28 AM, Timur Tabi wrote: > Grant Likely wrote: >> No. =A0It is a static property of the board/machine. =A0It 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 i= tself. > =A0If 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 program= ming > instead of SPD. =A0You can safely avoid SPD only if the DDR chips are sol= dered on > the board. Correct, if a real EDID i2c channel exists, then an edid property should *not* be specified in the device tree. g. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Date: Thu, 16 Dec 2010 17:42:21 +0000 Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Message-Id: List-Id: References: <1279893639-24333-1-git-send-email-agust@denx.de> <1279893639-24333-6-git-send-email-agust@denx.de> <4D0A446E.5020600@freescale.com> <4D0A4C38.3010105@freescale.com> In-Reply-To: <4D0A4C38.3010105@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Timur Tabi Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org, Anatolij Gustschin , devicetree-discuss@lists.ozlabs.org On Thu, Dec 16, 2010 at 10:28 AM, Timur Tabi wrote: > Grant Likely wrote: >> No. =A0It is a static property of the board/machine. =A0It 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 i= tself. > =A0If 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 program= ming > instead of SPD. =A0You can safely avoid SPD only if the DDR chips are sol= dered on > the board. Correct, if a real EDID i2c channel exists, then an edid property should *not* be specified in the device tree. g. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f170.google.com (mail-iy0-f170.google.com [209.85.210.170]) by ozlabs.org (Postfix) with ESMTP id C022C1007D7 for ; Fri, 17 Dec 2010 04:42:42 +1100 (EST) Received: by iym14 with SMTP id 14so2186342iym.15 for ; Thu, 16 Dec 2010 09:42:41 -0800 (PST) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: <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> <4D0A4C38.3010105@freescale.com> From: Grant Likely Date: Thu, 16 Dec 2010 10:42:21 -0700 Message-ID: Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID To: Timur Tabi Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org, Anatolij Gustschin , devicetree-discuss@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Dec 16, 2010 at 10:28 AM, Timur Tabi wrote: > Grant Likely wrote: >> No. =A0It is a static property of the board/machine. =A0It is expected i= t >> to be encoded into the board's .dts file. > > Ok, but that only makes sense if the monitor is hard-wired to the board i= tself. > =A0If 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 program= ming > instead of SPD. =A0You can safely avoid SPD only if the DDR chips are sol= dered on > the board. Correct, if a real EDID i2c channel exists, then an edid property should *not* be specified in the device tree. g.