DVI-D and HDMI is one and the same thing seen from an electrical and video
format point of view.
However there is a difference in supported video modes - Many (if not all?)
monitors support reduced timing (giving shorter blanking intervals, and
thereby better bandwidth utilization), while not all TV's support this.
Unfortunately "full timing" is first supported by the OMAP from ES3.1 (maybe
ES3.0) which is mounted on Rev C (and B7 AFAIK) of the Beagle...
Best regards
Søren
> On Wed, Feb 25, 2009 at 2:54 PM, priyanka sharma <priya...@gmail.com> wrote:
>> hi,
>> thanks for the reply. But I think that the patch may not work for all the
>> TV's. Here I am using LG Xcanvas TV. Is there some way to find out which
>> pixel clock rate the Tv supports ?
>> Also could you tell us from where we should check out the kernel source
>> code?
>>
>> thanks
>>
>
> Hi, You need to understand that Beagleboard has DVI-D over HDMI
> interface. As per my understanding, you either need to HDMI to DVI-D
> cable (avaiable in local market too) and DVI-D compatiable monitor.
Please, please stop spreading these misconceptions. HDMI and DVI-D
signals are EXACTLY THE SAME. The only difference is the connector.
The Beagle does not support HDMI audio, but this has *no* impact on
the video signal.
It is true that the driver currently in the linux-omap tree do not
support all possible timings, which does lead to problems with certain
TVs/monitors. This has nothing to do with HDMI vs. DVI; it is purely
a driver limitation that is removed with the new DSS2 drivers.
--
Måns Rullgård
ma...@mansr.com
Mans, Thanks for clarrification.
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.gitrequire some changes for OTG support?