<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Elijah Miller&#8217;s NEC v30 on a Pi hat	</title>
	<atom:link href="https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/feed/" rel="self" type="application/rss+xml" />
	<link>https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/</link>
	<description>Fun with Virtualization</description>
	<lastBuildDate>Sat, 05 Jun 2021 10:08:57 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>
		By: p2mate		</title>
		<link>https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/comment-page-1/#comment-274201</link>

		<dc:creator><![CDATA[p2mate]]></dc:creator>
		<pubDate>Sat, 05 Jun 2021 10:08:57 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=11104#comment-274201</guid>

					<description><![CDATA[Obviously reducing the timer tick frequency will make the computer look faster for SI because SI uses this timer as its clock. Given that the timer period on an XT was  1.19318MHz / 65536,  I think usleep(33927) should be a more accurate emulation. However this doesn&#039;t account for extra delays introduced by thread scheduling etc.]]></description>
			<content:encoded><![CDATA[<p>Obviously reducing the timer tick frequency will make the computer look faster for SI because SI uses this timer as its clock. Given that the timer period on an XT was  1.19318MHz / 65536,  I think usleep(33927) should be a more accurate emulation. However this doesn&#8217;t account for extra delays introduced by thread scheduling etc.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/comment-page-1/#comment-274156</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Fri, 04 Jun 2021 05:47:04 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=11104#comment-274156</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/comment-page-1/#comment-274152&quot;&gt;raijinkai&lt;/a&gt;.

I remember something about some universal hotplug system, in some way this is what PReP/CHrP was a generic PC with a different processor but where it fell flat was it being tied to POWER instead of allowing different processors, let alone something like the &lt;a href=&quot;https://www.theregister.com/1998/10/01/microsoft_killed_the_powerpc/&quot; rel=&quot;nofollow ugc&quot;&gt;PowerPC 615&lt;/a&gt;.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/comment-page-1/#comment-274152">raijinkai</a>.</p>
<p>I remember something about some universal hotplug system, in some way this is what PReP/CHrP was a generic PC with a different processor but where it fell flat was it being tied to POWER instead of allowing different processors, let alone something like the <a href="https://www.theregister.com/1998/10/01/microsoft_killed_the_powerpc/" rel="nofollow ugc">PowerPC 615</a>.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: raijinkai		</title>
		<link>https://virtuallyfun.com/2021/06/04/elijah-millers-nec-v30-on-a-pi-hat/comment-page-1/#comment-274152</link>

		<dc:creator><![CDATA[raijinkai]]></dc:creator>
		<pubDate>Fri, 04 Jun 2021 03:53:18 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=11104#comment-274152</guid>

					<description><![CDATA[AMD Hypertransport bus had provisions to connect different architecture CPUs to the same bus, with full interaction between them in master/slave configuration (Boot CPU and its &quot;coprocessor&quot;). It was said to give PCs the same powers than Amiga had years back with its Zorro bus compatible with &quot;personality&quot; CPU cards. Unfortunately this never got any mainstream board implementation, besides some rare Xilinx networking accelerators sold in 200x. Would have been nice to team it with virtualization extensions to have &quot;Accelerated&quot; VM sessions of any architecture, as long as there would be a &quot;personality card&quot; available for it. Imagine having in the same x86_64-PC &quot;accelerated&quot; VM sessions booting ARM, RiscV, SPARC, PPC (was the main objective back then, in order to emulate macOS PPC)...]]></description>
			<content:encoded><![CDATA[<p>AMD Hypertransport bus had provisions to connect different architecture CPUs to the same bus, with full interaction between them in master/slave configuration (Boot CPU and its &#8220;coprocessor&#8221;). It was said to give PCs the same powers than Amiga had years back with its Zorro bus compatible with &#8220;personality&#8221; CPU cards. Unfortunately this never got any mainstream board implementation, besides some rare Xilinx networking accelerators sold in 200x. Would have been nice to team it with virtualization extensions to have &#8220;Accelerated&#8221; VM sessions of any architecture, as long as there would be a &#8220;personality card&#8221; available for it. Imagine having in the same x86_64-PC &#8220;accelerated&#8221; VM sessions booting ARM, RiscV, SPARC, PPC (was the main objective back then, in order to emulate macOS PPC)&#8230;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
