<?xml version="1.0"?>
<rss version="2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:neowin="https://www.neowin.net/">
	<channel>
		<title>Neowin News Feed for: Hbm3</title>
		<link>https://www.neowin.net/news/tag/hbm3/</link>
        <atom:link href="https://www.neowin.net/news/rss/hbm3/" rel="self" type="application/rss+xml" />
		<description>Neowin News Feed for: Hbm3</description>
		<language>en-us</language>
		<generator>Neowin Ignition News</generator>
		<managingEditor>editor@neowin.net (Managing Editor)</managingEditor>
		<webMaster>developers@neowin.net (Neowin Developers)</webMaster>
		<ttl>5</ttl>
		<image>
			<title>Neowin.net</title>
			<url>https://www.neowin.net/images/pegasus/icon.png</url>
			<link>https://www.neowin.net</link>
		</image>
		        <item>
            <title>Next-gen HBM3 details inadvertently leaked by SK hynix</title>
            <link>https://www.neowin.net/news/next-gen-hbm3-details-inadvertently-leaked-by-sk-hynix/</link>
            <description>&lt;div style="float:left;margin-right:10px;"&gt;&lt;img src="https://cdn.neowin.com/news/images/uploaded/2021/06/1623297011_hbm2e_vs_hbm3_medium.jpg" alt="" /&gt;&lt;/div&gt;SK hynix recently updated its website and it appears to have inadvertently leaked some of the details of next-gen 3D stacked HBM3. The new memory will be close to 50% faster than the current HBM2E. &lt;a href="https://www.neowin.net/news/next-gen-hbm3-details-inadvertently-leaked-by-sk-hynix/"&gt;Read more...&lt;/a&gt;</description>
            <author>Sayan Sen</author>
            <pubDate>Thu, 10 Jun 2021 05:24:01 +0000</pubDate>
            <guid>https://www.neowin.net/news/next-gen-hbm3-details-inadvertently-leaked-by-sk-hynix/</guid>
            <media:thumbnail url="https://cdn.neowin.com/news/images/uploaded/2021/06/1623297011_hbm2e_vs_hbm3_story.jpg" width="760" height="428" />
            <neowin:tags>#hbm3 #hbm2e #hbm #skhynix</neowin:tags>            <neowin:twitter>@ssc_combater007</neowin:twitter>        </item>
        	</channel>
</rss>
