<?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: Work plan for M3 2020</title>
	<atom:link href="http://thetarpit.org/2020/work-plan-for-m3-2020/feed" rel="self" type="application/rss+xml" />
	<link>http://thetarpit.org/2020/work-plan-for-m3-2020</link>
	<description>"Now I feel like I know less about what that blog is about than I did before."</description>
	<pubDate>Sun, 05 Apr 2026 19:51:48 +0000</pubDate>
	<generator>http://thetarpit.org</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: spyked</title>
		<link>http://thetarpit.org/2020/work-plan-for-m3-2020#comment-268</link>
		<dc:creator>spyked</dc:creator>
		<pubDate>Wed, 11 Mar 2020 09:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=358#comment-268</guid>
		<description>&gt; Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch.

Sounds great, looking forward to giving it a test run.

&gt; with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21

Noted, although I'm not sure if there are any changes between the two version that I should be aware of in particular.

&gt; What's your eta on the updated plan ?

I'll say the end of the month, although I hope to deliver it earlier. Given the new info about TRB on Gales, I probably won't have much of a plan to lay out for this particular task. However, I must confess mapping hardware has been quite tricky so far, especially for AMD, which doesn't seem to have any centralized place to look for hardware -- there is an official one for &lt;a href="https://ark.intel.com" rel="nofollow"&gt;Intel&lt;/a&gt; and it's been quite easy to look through so far, although there's still quite a bit of work on that front as well. So for now I want to take a step back and take another look at the criteria for "TMSR-OS bootable hardware" so that it can help me in this search.

&gt; Sorry to hear about that, hope you've recovered.

Thanks! I'm back on my feet, though still taking it slowly for the moment.</description>
		<content:encoded><![CDATA[<p>> Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch.</p>
<p>Sounds great, looking forward to giving it a test run.</p>
<p>> with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21</p>
<p>Noted, although I'm not sure if there are any changes between the two version that I should be aware of in particular.</p>
<p>> What's your eta on the updated plan ?</p>
<p>I'll say the end of the month, although I hope to deliver it earlier. Given the new info about TRB on Gales, I probably won't have much of a plan to lay out for this particular task. However, I must confess mapping hardware has been quite tricky so far, especially for AMD, which doesn't seem to have any centralized place to look for hardware -- there is an official one for <a href="https://ark.intel.com" rel="nofollow">Intel</a> and it's been quite easy to look through so far, although there's still quite a bit of work on that front as well. So for now I want to take a step back and take another look at the criteria for "TMSR-OS bootable hardware" so that it can help me in this search.</p>
<p>> Sorry to hear about that, hope you've recovered.</p>
<p>Thanks! I'm back on my feet, though still taking it slowly for the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robinson Dorion</title>
		<link>http://thetarpit.org/2020/work-plan-for-m3-2020#comment-266</link>
		<dc:creator>Robinson Dorion</dc:creator>
		<pubDate>Mon, 09 Mar 2020 18:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://thetarpit.org/?p=358#comment-266</guid>
		<description>&lt;blockquote&gt;
at the moment I have absolutely no idea how much time it'd take to stand up a TRB node on Gales
&lt;/blockquote&gt;

Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch. A part from that he also has a patch to the makefiles to remove the rotor orchestra since Gales is musl. He has a deadline of Thursday to get these published in preparation for MP using GBW. So, once you have the patches, TRB is operable on Gales and takes less time and overhead than building TRB with rotor (with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21). 

&lt;blockquote&gt;
I'm committing to properly laying out how and where my time gets wasted and getting out at the very least a draft plan2 for the two items above.
&lt;/blockquote&gt;

Ok, looking forward to it. What's your eta on the updated plan ?

&lt;blockquote&gt;
Not even mentioning that the beginning of March hit me with a flu which sapped me of energy for almost a week.
&lt;/blockquote&gt;

Sorry to hear about that, hope you've recovered.</description>
		<content:encoded><![CDATA[<blockquote><p>
at the moment I have absolutely no idea how much time it'd take to stand up a TRB node on Gales
</p></blockquote>
<p>Jacob has a patch to boost so it builds with the gcc-4.7.4-demangler-amputation.patch. A part from that he also has a patch to the makefiles to remove the rotor orchestra since Gales is musl. He has a deadline of Thursday to get these published in preparation for MP using GBW. So, once you have the patches, TRB is operable on Gales and takes less time and overhead than building TRB with rotor (with the caveat that TRB w/ rotor uses musl-1.1.8 and Gales uses musl-1.1.21). </p>
<blockquote><p>
I'm committing to properly laying out how and where my time gets wasted and getting out at the very least a draft plan2 for the two items above.
</p></blockquote>
<p>Ok, looking forward to it. What's your eta on the updated plan ?</p>
<blockquote><p>
Not even mentioning that the beginning of March hit me with a flu which sapped me of energy for almost a week.
</p></blockquote>
<p>Sorry to hear about that, hope you've recovered.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
