<?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: Qualcomm showers Europe with money</title>
	<atom:link href="http://www.blackberrycool.com/2007/05/qualcomm-showers-europe-with-money/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blackberrycool.com/2007/05/qualcomm-showers-europe-with-money/</link>
	<description>The voice of the BlackBerry community.</description>
	<pubDate>Fri, 09 Jan 2009 06:26:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: BlackBerry Cool &#187; Qualcomm shares 3G love with Sagem</title>
		<link>http://www.blackberrycool.com/2007/05/qualcomm-showers-europe-with-money/#comment-139701</link>
		<dc:creator>BlackBerry Cool &#187; Qualcomm shares 3G love with Sagem</dc:creator>
		<pubDate>Thu, 07 Jun 2007 13:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackberrycool.com/2007/05/24/004584/#comment-139701</guid>
		<description>[...] While WCDMA might not be rocking the kasbah right now, it might get a kick in the pants with a little help from Sagem, who just struck a royalty-based deal with Qualcomm to develop WCDMA hardware. This falls well in line with recent incentives Qualcomm has put forward to develop WCDMA in Europe. If the Nokia fight is slowing down 3G progress, at least Qualcomm&#8217;s got some alternative direction. [...]</description>
		<content:encoded><![CDATA[<p>[...] While WCDMA might not be rocking the kasbah right now, it might get a kick in the pants with a little help from Sagem, who just struck a royalty-based deal with Qualcomm to develop WCDMA hardware. This falls well in line with recent incentives Qualcomm has put forward to develop WCDMA in Europe. If the Nokia fight is slowing down 3G progress, at least Qualcomm&#8217;s got some alternative direction. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
