<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>256-bit &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://wordpress.com/tag/256-bit/</link>
	<description>Feed of posts on WordPress.com tagged "256-bit"</description>
	<pubDate>Tue, 18 Nov 2008 21:03:40 +0000</pubDate>

	<generator>http://wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[HD Fujitsu 500GB com encriptação AES 256-bit on the fly!]]></title>
<link>http://keaton.wordpress.com/2008/11/13/hd-fujitsu-500gb-com-encriptacao-aes-256-bit-on-the-fly/</link>
<pubDate>Thu, 13 Nov 2008 10:30:50 +0000</pubDate>
<dc:creator>Keaton</dc:creator>
<guid>http://keaton.wordpress.com/2008/11/13/hd-fujitsu-500gb-com-encriptacao-aes-256-bit-on-the-fly/</guid>
<description><![CDATA[
A Fujitsu lançará um HD 2.5&#8243; com 500GB. Seria um HD comum se não fosse a encriptação AES]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p><img alt="" src="http://i368.photobucket.com/albums/oo122/KeatonX2/keaton_wordpress_com/fujitsu.jpg" class="aligncenter" width="320" height="197" /><br />
A Fujitsu lançará um HD 2.5&#8243; com 500GB. Seria um HD comum se não fosse a encriptação AES 256-bit on the fly (esse é o primeiro da categoria!), deleção dos dados em menos de 1 segundo e fato que ele também não tem halogenio. E é compativel com o RoHS&#8230;</p>
<p><strong>Fonte:</strong> <a href="http://www.marketwatch.com/news/story/Fujitsu-Release-New-Energy-Efficient/story.aspx?guid={56E1424A-7D1F-489F-899D-72D04243F7DF}" target="_blank">Market Watch</a><br />
*Advanced Encryption Standard.</p>
</div>]]></content:encoded>
</item>
<item>
<title><![CDATA[Some Radeon 5870 rumours are BS... some aren't ;)]]></title>
<link>http://theovalich.wordpress.com/2008/11/03/some-radeon-5870-rumours-are-bs-some-arent/</link>
<pubDate>Mon, 03 Nov 2008 21:59:07 +0000</pubDate>
<dc:creator>theovalich</dc:creator>
<guid>http://theovalich.wordpress.com/2008/11/03/some-radeon-5870-rumours-are-bs-some-arent/</guid>
<description><![CDATA[I&#8217;ve received word from a reader that some Germans wrote a story  containing details about RV]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p>I&#8217;ve received word from a reader that some Germans wrote a story  containing details about RV870, e.g. Radeon &#8220;5870&#8243;. <a href="http://www.neoseeker.com/news/9078-ati-hd5870-rumors-1-5-tflops-40nm-1000-shaders-and-multi-core-/" target="_blank">Neoseeker brought the translation forward</a> , and while some parts make a lot of sense, some really don&#8217;t.<br />
First of all, the RV870 is supposed to be a 40nm part, but that&#8217;s not something that we didn&#8217;t know already. Both Nvidia and AMD are going to bring 40nm half-node parts first, followed by 32 and 28nm full-nodes. According to the story, the GPU is supposed to contain 25% more shaders than Radeon 4800 series, bringing the theoretical computational power to 1.5 TFLOPS.<br />
Well, you don&#8217;t need 25% more shaders to get 50% performance increase. Radeon 4800 showed the path that the company is going to take, and the name of the game is how to increase the performance of those 10 shaders that now sit in one &#8220;pipeline&#8221; (or shader cluster), and increase the capacity of scratch cache to enable faster GPGPU computation.<br />
The alleged die size is 205mm2, and that would go in-line with die-shrink of 4800, which would be roughly 170mm2 if it was manufactured in 40nm (instead of actual 256mm2). 30-35mm2 should be enough to slap around 1000-1200 shaders, if those rumors are true.<br />
However, there is just one thing that does not hold ground in the story - and that is that RV870 should use 512-bit memory interface and GDDR5 memory. I may be forced to eat my own words, but no, ATI RV870 will not bring 512-bit memory controller. RV870 will feature much improved 256-bit memory controller, and it will offer bandwidth of some 150-200 GB/s per GPU. When you combine the two GPUs, possibly on the same substrate, you will get 512-bit memory controller&#8230; in a way. 512-bit memory controller with current GDDR5 memory (900 MHz QDR, e.g. 3.6 &#8220;GHz&#8221;) yields 230 GB/s. And that is the amount of bandwidth GTX280 would have if nV went for GDDR5 instead of older GDDR3 memory.<br />
Nvidia&#8217;s next-gen part will however, bring 512-bit memory controller coupled with GDDR5 memory, offering insane amount of bandwidth - 200-250 GB/s, to be more precise.</p>
<div id="attachment_302" class="wp-caption alignright" style="width: 310px"><a href="http://theovalich.wordpress.com/files/2008/11/intelpentiumdsmithfield.jpg"><img class="size-full wp-image-302" title="intelpentiumdsmithfield" src="http://theovalich.wordpress.com/files/2008/11/intelpentiumdsmithfield.jpg" alt="Dual-die GPU is a good idea, but can TSMC pack the chips like Intel can?" width="300" height="251" /></a><p class="wp-caption-text">Dual-die GPU is a good idea, but can TSMC pack the chips like Intel can?</p></div>
<p>It will be interesting to see can TSMC pack two RV870s on the same substrate, or that idea will go the way of do-do birds. We&#8217;ll see.<br />
Oh yeah, cooling will be vapor chamber, and we should see some really interesting cooling designs. AMD already got its feet wet with vapor-chamber technology (both 4870X2 and Sapphire&#8217;s Atomic 3870 and 4870 come with vapor chamber cooling).<br />
According to the story, the codename for the 5800 board is Lil&#8217; Dragon. However, claim about DX11 being ready in summer of 2009 is something that I would take with a big grain of salt. During PDC&#8217;08, held last week in LA, there were talk that Microsoft will even send Windows 7 to manufacturing without DirectX 11, putting 10.1 until DirectX 11 shows up at later date. My sources compared the situation for 2009 equal to the one in 2002, when ATI shipped DirectX 9 part five months before DX9 came out.<br />
As it stands right now, both Nvidia and ATI will have their DX11 parts ahead of actual API, giving developers enough time to optimize their respective drivers. Let&#8217;s hope for the best.</p>
</div>]]></content:encoded>
</item>
<item>
<title><![CDATA[TrueCrypt]]></title>
<link>http://haersmith.wordpress.com/2008/08/06/truecrypt/</link>
<pubDate>Wed, 06 Aug 2008 02:12:04 +0000</pubDate>
<dc:creator>Haersmith</dc:creator>
<guid>http://haersmith.wordpress.com/2008/08/06/truecrypt/</guid>
<description><![CDATA[Protégez vos données avec ce logiciel d&#8217;encryption gratuit !


TrueCrypt est un outil d]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p>Protégez vos données avec ce logiciel d&#8217;encryption gratuit !</p>
<p><!--more--></p>
<p style="text-align:center;"><a href="http://haersmith.files.wordpress.com/2008/08/xps_wizardciphers.png"><img class="aligncenter size-medium wp-image-372" src="http://haersmith.wordpress.com/files/2008/08/xps_wizardciphers.png?w=300" alt="" width="300" height="184" /></a></p>
<p>TrueCrypt est un outil d&#8217;encryption de disque à la volée (particulièrement utile pour les disques dur externe), le disque en question peut être un fichier monté comme un disque virtuel ou bien un disque dur existant.</p>
<p>Le logiciel est orienté vers une sécurité maximale et les données sont encryptées à la volée au moment ou elles sont stockées. Lorsque les données sont cryptées avec l&#8217;un des nombreux algorithmes d&#8217;encryption proposés (Blowfish, AES-256, CAST5, Tripe DES&#8230;), l&#8217;ouverture du fichier ou du disque dur ne fait rien apparaître d&#8217;autre qu&#8217;une série de chiffres aléatoires. A noter qu&#8217;en plus d&#8217;être crypté, le volume peut aussi être masqué. La création d&#8217;un volume se fait par le biais d&#8217;un assistant clair.</p>
<p>A l&#8217;usage, le volume encrypté est vu par le système comme un disque classique et en possède toutes les caractéristiques, il faudra simplement saisir le mot de passe associé au volume au moment du &#8220;montage&#8221; de celui-ci.</p>
<p>En clair : un indispensable !</p>
<p style="text-align:center;"><a href="http://www.truecrypt.org/" target="_blank"><strong>Cliquez ici pour allez sur le site officiel !</strong></a></p>
</div>]]></content:encoded>
</item>
<item>
<title><![CDATA[AMD RV870: Especificaciones]]></title>
<link>http://aledb12.wordpress.com/2008/07/18/amd-rv870-especificaciones/</link>
<pubDate>Fri, 18 Jul 2008 21:30:05 +0000</pubDate>
<dc:creator>aledb12</dc:creator>
<guid>http://aledb12.wordpress.com/2008/07/18/amd-rv870-especificaciones/</guid>
<description><![CDATA[
Los rumores en Asia apuntan a que RV870 será un paso evolucionario y que apunta a la reducción de]]></description>
<content:encoded><![CDATA[<div class='snap_preview'><p style="text-align:center;"><img class="size-full wp-image-959 aligncenter" src="http://aledb12.wordpress.com/files/2008/05/44402a_atr_prem_logo_l_e_rgb.png" alt="" width="252" height="234" /></p>
<p style="text-align:justify;">Los rumores en Asia apuntan a que RV870 será un paso evolucionario y que apunta a la reducción del tamaño del chip base RV770.<br />
<!--more--></p>
<p style="text-align:justify;">RV870 será construido por TSMC en 40nm, su área sera de 140mm<sup>2</sup> la cual es bastante menor que la de RV770 (260mm<sup>2</sup>). Se sabe que tendrá 192 ALUs, tal como en RV770 cada ALU puede procesar 5 operaciones lo que nos da un total de 960SP.</p>
<p style="text-align:justify;">Para mantener un die pequeño el chip aun posee 256-Bit de Bus, se estima que el núcleo será un 20% mas rápido que RV770 pero siempre sujeto a las frecuencias finales.</p>
<p>También se dice que AMD usará un nuevo diseño en R800, el cual al parecer seria un chip con 2 núcleos en el y no una tarjeta dual GPU con ambos GPUs separados en el PCB.</p>
<p>Fuente: <strong><a href="http://en.hardspell.com/doc/showcont.asp?news_id=3768" target="_blank">Hardspell</a></strong> via <a href="http://www.chw.net/foro/especificaciones-de-amd-rv870-t169261.html" target="_blank"><strong>CHW</strong><br />
</a></p>
</div>]]></content:encoded>
</item>

</channel>
</rss>
