{"type":"note","self":"https:\/\/digitigrade.xn--80andq.net\/note\/1868","created":"2026-05-18T02:49:53+01:00","modified":null,"author":"https:\/\/digitigrade.xn--80andq.net\/actor\/1","summary":null,"plainContent":"thinking about a hardware varvara computer. with like homemade chips and stuff\ni imagine it&#039;d have an &quot;uxn cpu&quot; that would communicate through busses with the main memory and a &quot;device controller&quot; . the device controller would also be able to interrupt the cpu with a particular address to jump to, except it isn&#039;t really an interrupt because in uxn land generally everything runs to completion before doing anything else? i suppose you could try having the cpu save its context (mostly just the stacks) for real interrupts but it might cause problems with any code that modifies itself a lot or expects memory not to change under its feet","formattedContent":{"text\/html":"<p>thinking about a hardware varvara computer. with like homemade chips and stuff<br>i imagine it'd have an &quot;uxn cpu&quot; that would communicate through busses with the main memory and a &quot;device controller&quot; . the device controller would also be able to interrupt the cpu with a particular address to jump to, except it isn't really an interrupt because in uxn land generally everything runs to completion before doing anything else? i suppose you could try having the cpu save its context (mostly just the stacks) for real interrupts but it might cause problems with any code that modifies itself a lot or expects memory not to change under its feet<\/p>\n","text\/markdown":"thinking about a hardware varvara computer. with like homemade chips and stuff\ni imagine it'd have an \"uxn cpu\" that would communicate through busses with the main memory and a \"device controller\" . the device controller would also be able to interrupt the cpu with a particular address to jump to, except it isn't really an interrupt because in uxn land generally everything runs to completion before doing anything else? i suppose you could try having the cpu save its context (mostly just the stacks) for real interrupts but it might cause problems with any code that modifies itself a lot or expects memory not to change under its feet"},"language":"en_GB","mentions":[],"inReplyTo":null,"threadApex":null,"privacy":{"scope":"public","alsoVisibleTo":[],"indexable":true,"canReshare":"all","canReply":"all","canOtherInteract":"all"},"attachments":[],"extensions":{"https:\/\/pawpub.entities.org.uk\/extension\/link-previews":[]}}