From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org,
Anatolij Gustschin <agust@denx.de>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using
Date: Thu, 16 Dec 2010 17:28:24 +0000 [thread overview]
Message-ID: <4D0A4C38.3010105@freescale.com> (raw)
In-Reply-To: <AANLkTinOf__X0p3_5G90KkYS9PXpB2j0_06MFhFcZzqO@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, linux-fbdev@vger.kernel.org,
Anatolij Gustschin <agust@denx.de>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID
Date: Thu, 16 Dec 2010 11:28:24 -0600 [thread overview]
Message-ID: <4D0A4C38.3010105@freescale.com> (raw)
In-Reply-To: <AANLkTinOf__X0p3_5G90KkYS9PXpB2j0_06MFhFcZzqO@mail.gmail.com>
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
next prev parent reply other threads:[~2010-12-16 17:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 14:00 [PATCH v4 0/5] Rework MPC5121 DIU support (for 2.6.36) Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2010-07-28 7:02 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area Grant Likely
2010-07-28 7:02 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Grant Likely
2010-07-28 7:02 ` Grant Likely
[not found] ` <AANLkTikkLVCxU4ZC_nmUhKTQogUNeQzxOX6KqgZcxiYr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-28 7:56 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area Anatolij Gustschin
2010-07-28 7:56 ` [PATCH v4 1/5] fsl-diu-fb: fix issue with re-enabling DIU area descriptor Anatolij Gustschin
2010-07-28 7:56 ` Anatolij Gustschin
[not found] ` <AANLkTikkLVCxU4ZC_nmUhKTQogUNeQzxOX6KqgZcxiYr__2540.83384429595$1280300644$gmane$org@mail.gmail.com>
2010-07-29 11:48 ` Detlev Zundel
2010-07-23 14:00 ` [PATCH v4 2/5] fsl-diu-fb: move fsl-diu-fb.h to include/linux Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 3/5] powerpc/mpc5121: shared DIU framebuffer support Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2011-12-15 17:27 ` Tabi Timur-B04825
2011-12-15 21:26 ` Anatolij Gustschin
2011-12-16 18:24 ` Timur Tabi
2011-12-16 22:59 ` Anatolij Gustschin
2011-12-16 23:00 ` Timur Tabi
2010-07-23 14:00 ` [PATCH v4 4/5] powerpc: doc/dts-bindings: update doc of FSL DIU bindings Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
2010-07-23 14:00 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Anatolij Gustschin
2010-07-23 14:00 ` Anatolij Gustschin
[not found] ` <1279893639-24333-6-git-send-email-agust-ynQEQJNshbs@public.gmane.org>
2010-12-16 16:47 ` Timur Tabi
2010-12-16 16:47 ` Timur Tabi
2010-12-16 16:47 ` Timur Tabi
[not found] ` <AANLkTin-TL5_TKnyHYtZdixosfqpkPNoarSTC+K4tTUb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-16 16:53 ` Grant Likely
2010-12-16 16:53 ` Grant Likely
2010-12-16 16:53 ` Grant Likely
2010-12-16 16:55 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using Timur Tabi
2010-12-16 16:55 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Timur Tabi
[not found] ` <4D0A446E.5020600-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2010-12-16 17:06 ` Grant Likely
2010-12-16 17:06 ` Grant Likely
2010-12-16 17:06 ` Grant Likely
2010-12-16 17:28 ` Timur Tabi [this message]
2010-12-16 17:28 ` Timur Tabi
2010-12-16 17:42 ` Grant Likely
2010-12-16 17:42 ` Grant Likely
2010-12-16 17:42 ` Grant Likely
2010-12-16 17:42 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using Anatolij Gustschin
2010-12-16 17:42 ` [PATCH v4 5/5] fsl-diu-fb: Support setting display mode using EDID Anatolij Gustschin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0A4C38.3010105@freescale.com \
--to=timur@freescale.com \
--cc=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-fbdev@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.