From mboxrd@z Thu Jan 1 00:00:00 1970 From: "K, Mythri P" Date: Fri, 25 Mar 2011 13:46:05 +0000 Subject: Re: [RFC PATCH] HDMI:Support for EDID parsing in kernel. Message-Id: List-Id: References: <1300815176-21206-1-git-send-email-mythripk@ti.com> <20110323081820.5b37d169@jbarnes-desktop> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Guennadi Liakhovetski Cc: Jesse Barnes , Dave Airlie , linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org, dri-devel , linux-media@vger.kernel.org Hi Gunnedi, >> > Dave's point is that we can't ditch the existing code without >> > introducing a lot of risk; it would be better to start a library-ized >> > EDID codebase from the most complete one we have already, i.e. the DRM >> > EDID code. > > Does the DRM EDID-parser also process blocks beyond the first one and > also parses SVD entries similar to what I've recently added to fbdev? Yes, > we definitely need a common EDID parses, and maybe we'll have to collect > various pieces from different implementations. > As far as I know , it does not parse SVD ,But it should not be that difficult to add. We could take the SVD parsing from your code . In the RFC i have posted I parse for detailed timing and other VSDB blocks. Also the parsing should be based on the extension type for multiple 128 byte blocks. Thanks and regards, Mythri. > Thanks > Guennadi >