<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: DisplayPort Really Is The Future</title>
	<atom:link href="http://adterrasperaspera.com/blog/2006/06/28/displayport-really-is-the-future/feed" rel="self" type="application/rss+xml" />
	<link>http://adterrasperaspera.com/blog/2006/06/28/displayport-really-is-the-future</link>
	<description>Transmissions from the Little Blue Marble</description>
	<pubDate>Thu, 08 Jan 2009 13:19:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: tantrik</title>
		<link>http://adterrasperaspera.com/blog/2006/06/28/displayport-really-is-the-future#comment-124807</link>
		<dc:creator>tantrik</dc:creator>
		<pubDate>Tue, 05 Feb 2008 20:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adterrasperaspera.com/blog/2006/06/28/displayport-really-is-the-future/#comment-124807</guid>
		<description>Easier to implement ? Who are you kidding. DisplayPort has multiple clock domains, requires clock extraction, a fixed link speed does make the frequency dependant losses a slight more manageable, however, still requires just about the same amount of silicon.

HDCP is an Intel license. Most DVD's / TV's have HDCP, so DisplayPort will have licensing costs also.

HDMI1.3 has 10.2Gbps vs DisplayPort 10.7. Not much of a difference bandwidth wise.</description>
		<content:encoded><![CDATA[<p>Easier to implement ? Who are you kidding. DisplayPort has multiple clock domains, requires clock extraction, a fixed link speed does make the frequency dependant losses a slight more manageable, however, still requires just about the same amount of silicon.</p>
<p>HDCP is an Intel license. Most DVD&#8217;s / TV&#8217;s have HDCP, so DisplayPort will have licensing costs also.</p>
<p>HDMI1.3 has 10.2Gbps vs DisplayPort 10.7. Not much of a difference bandwidth wise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
