Whole-known-network
<p>Okay, let's try this, for the first time ever. I'm Quin, and I'm looking for a job over the summer, possibly longer as long as it's part time (I'm a college student with the summer off). I'm mostly interested in <a href="https://dragonscave.space/tags/remote" class="mention hashtag" rel="tag">#<span>remote</span></a> work, due to my complete blindness traveling to a workplace is more difficult, all be it not impossible. I just prefer coding from my bedroom. I'm a software developer and hacker (in the oldest and best sense of the word) who loves nothing more than figuring out a good challenge. I prefer low-level coding in C, C++, Rust, etc., but things like Python and Lua have their place too. My resume is here: <a href="https://quinbox.xyz/resume.html" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">quinbox.xyz/resume.html</span><span class="invisible"></span></a><br /><a href="https://dragonscave.space/tags/FediHire" class="mention hashtag" rel="tag">#<span>FediHire</span></a> <a href="https://dragonscave.space/tags/fediHired" class="mention hashtag" rel="tag">#<span>fediHired</span></a></p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> Doable but you're limited by the 35T's fairly large clock regions which I think would present problems in a practical implementation.</p><p>I'm a big fan of "poor man's partial reconfig" for this sort of thing (using SRL32s as serially reconfigurable LUT5s).</p><p>For example, one SRL can implement up to a 5:1 mux in a single LUT without using any DFFs in the logic area.</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> RTL and partial reconfig :p</p>
<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> What I don't know is what the cleanest programming model for an end user developing triggers for this is going to look like.</p>
<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> Lol.</p><p>A VLIW processor may actually end up being the logical implementation of this. Who knows.</p><p>But the more I think about it, the more I lean towards a two-part system with a bunch of parallel function blocks that output one or more bits every cycle (each block having a bunch of config registers to specify muxing and thresholds and such), then a serial state machine operating on their output.</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> guess we doin HDL now. Once I finish these damn boards</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> I joked about it being a quasi CPU and it is quickly becoming straight up a CPU, I love it</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> Exactly what I was getting at. It's solvable, but not trivial.</p><p>You'll probably need multiple replicated copies of the logic and some speculation or replication to handle multiple cases in parallel then figure out what happened the next cycle or something.</p>
<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@aleksorsist" class="u-url mention">@<span>aleksorsist</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@urja" class="u-url mention">@<span>urja</span></a></span> you would unroll the state machine N times and pipeline, I think</p>