Haru Nakamura 🏳️⚧️
@nakamura.cryptoanarchy.network
[Software | Gamedev | CompSci | Electronics | Musician]
• 29, pre-HRT, ΘΔ.
• She/Her/It
• Chile
• Discord: nakamura.systems (moots only)
• Synthetic Mizutsune
Heart, conviction, respect, and attitude.
Posts/Reposts SFW, likes NSFW.
• 29, pre-HRT, ΘΔ.
• She/Her/It
• Chile
• Discord: nakamura.systems (moots only)
• Synthetic Mizutsune
Heart, conviction, respect, and attitude.
Posts/Reposts SFW, likes NSFW.
Yknow, i did say I'd post about fixing my car as I did things, and I did do some soldering on the dashboard... but this thing is genuinely so simple and so boring I couldn't really find anything to talk about. There's no chips, no fancy components, nothing.
January 23, 2026 at 7:53 PM
Yknow, i did say I'd post about fixing my car as I did things, and I did do some soldering on the dashboard... but this thing is genuinely so simple and so boring I couldn't really find anything to talk about. There's no chips, no fancy components, nothing.
FINALLY. COOPERATIVE MULTITASKING!!
January 17, 2026 at 1:22 AM
FINALLY. COOPERATIVE MULTITASKING!!
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA hi.
January 17, 2026 at 12:11 AM
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA hi.
So, IrisOS. Because someone suggested it, I've been trying to implement cooperative multitasking and I'm going insane trying to do the context switching. My tasks run once, then the stack gets fucked and all I get is garbage. AAAAAAAAAAAAAA.
![Screenshot of QEMU running IrisOS. A bug is present causing memory stack corruption. Screen reads as follows:
0x7b100x7b100x8000
[OK] IrisFS: 50KB RAMDisk Ready
[OK] IRIS Scheduler - Multitasking
IrisOS Shell v0.0.1
Type 'help' for available commands
CMD> spawn
TaskA
TaskB
TaskC
[DEBUG] Spawned 3 tasks!
CMD> yield
[DEBUG] Yielding...
00101TaskA1[TASK A] Iteration 0
TaskA11202TaskB2[TASK B] Iteration 0
TaskB22303TaskC3[TASK C] Iteration 0
TaskC33425262720000CMD> _](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:u5kquvhmdb45amkwgz35pyh7/bafkreiel76rs5sdx4eicvsphxsbeyz76o7fbuvwbbi5aecotmqte6htwdu@jpeg)
January 16, 2026 at 8:32 PM
So, IrisOS. Because someone suggested it, I've been trying to implement cooperative multitasking and I'm going insane trying to do the context switching. My tasks run once, then the stack gets fucked and all I get is garbage. AAAAAAAAAAAAAA.
So, in a complete oopsies, I found out the sleep_ticks function I'd made for IrisOS is blocking.
Of course it is, it's just an empty block of code. I shouldn't write an OS while I'm half-asleep, so I ended up replacing it with busy_wait that instead executes NOPs on the CPU. No more blocking.
Of course it is, it's just an empty block of code. I shouldn't write an OS while I'm half-asleep, so I ended up replacing it with busy_wait that instead executes NOPs on the CPU. No more blocking.
January 16, 2026 at 10:28 AM
So, in a complete oopsies, I found out the sleep_ticks function I'd made for IrisOS is blocking.
Of course it is, it's just an empty block of code. I shouldn't write an OS while I'm half-asleep, so I ended up replacing it with busy_wait that instead executes NOPs on the CPU. No more blocking.
Of course it is, it's just an empty block of code. I shouldn't write an OS while I'm half-asleep, so I ended up replacing it with busy_wait that instead executes NOPs on the CPU. No more blocking.
okay, I've changed the order of priorities. Filesystem first, implemented as a ramdisk, NOW comes the Disk IO driver.
On that note, filesystem get. Meet IrisFS.
On that note, filesystem get. Meet IrisFS.
![Screenshot of QEMU VM running IrisOS.
Terminal reads as follows:
[OK] Mem: 0x68:c - Align: 0x68:c0x7000
[OK] IrFS: 50KB RAMDisk Ready
IrisOS Shell v0.0.1
Type 'help' for available commands
CMD> touch hi.txt
File hi.txt created
CMD> ls
Files in IrisFS:
hi.txt (0x0 bytes)
CMD> write hi.txt hello there!
Data written to hi.txt
CMD> cat hi.txt
hello there!
CMD> ls
Files in IrisFS:
hi.txt (0xc bytes)
CMD> _](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:u5kquvhmdb45amkwgz35pyh7/bafkreibavxihnqx7cxbn4yr4kazvdc64lkbkvopxnqgcnucubmrsbcod34@jpeg)
January 13, 2026 at 12:09 AM
okay, I've changed the order of priorities. Filesystem first, implemented as a ramdisk, NOW comes the Disk IO driver.
On that note, filesystem get. Meet IrisFS.
On that note, filesystem get. Meet IrisFS.
Instead of that, I made something else.
I improved my shell using a command table and proper handlers instead of a bunch of if-else in kernel.c, and added support for lowercase chars so that I'm not screaming at the kernel all the time.
This also may or may not be a shitpost in OS form.
WYSIWYG.
I improved my shell using a command table and proper handlers instead of a bunch of if-else in kernel.c, and added support for lowercase chars so that I'm not screaming at the kernel all the time.
This also may or may not be a shitpost in OS form.
WYSIWYG.
January 12, 2026 at 9:33 AM
Instead of that, I made something else.
I improved my shell using a command table and proper handlers instead of a bunch of if-else in kernel.c, and added support for lowercase chars so that I'm not screaming at the kernel all the time.
This also may or may not be a shitpost in OS form.
WYSIWYG.
I improved my shell using a command table and proper handlers instead of a bunch of if-else in kernel.c, and added support for lowercase chars so that I'm not screaming at the kernel all the time.
This also may or may not be a shitpost in OS form.
WYSIWYG.
OH! I haven't shown it actually being compiled and running. Hold on, let me fix that!
January 11, 2026 at 6:32 PM
OH! I haven't shown it actually being compiled and running. Hold on, let me fix that!
also funny ahh phoenix wright reference
January 11, 2026 at 6:26 PM
also funny ahh phoenix wright reference
So, because I wanted a boot image, I've implemented sleep ticks in timer.c - it just does nothing for a determined amount of ticks, and since it's running at 50Hz, I can do something like load a function that prints a boot splash and call sleep_ticks(250); to display it for 5 seconds.
January 11, 2026 at 6:21 PM
So, because I wanted a boot image, I've implemented sleep ticks in timer.c - it just does nothing for a determined amount of ticks, and since it's running at 50Hz, I can do something like load a function that prints a boot splash and call sleep_ticks(250); to display it for 5 seconds.
I also ran into a very funny bug with backspace due to the way I'm handling the cursor.
You might be expecting me to use the hardware cursor, but I'm not. It's being drawn through software. So, the bug is that it's inverting the color on every backspace, leaving a white block. Let's see if can fix.
You might be expecting me to use the hardware cursor, but I'm not. It's being drawn through software. So, the bug is that it's inverting the color on every backspace, leaving a white block. Let's see if can fix.
January 11, 2026 at 8:10 AM
I also ran into a very funny bug with backspace due to the way I'm handling the cursor.
You might be expecting me to use the hardware cursor, but I'm not. It's being drawn through software. So, the bug is that it's inverting the color on every backspace, leaving a white block. Let's see if can fix.
You might be expecting me to use the hardware cursor, but I'm not. It's being drawn through software. So, the bug is that it's inverting the color on every backspace, leaving a white block. Let's see if can fix.
I fixed it. Not only did I fix it, but it also means I was finally able to implement a shell. What was wrong? Well, I forgot to write the stub for the IRQs like the genius I am so they just weren't being handled at all.
The name of the OS and Kernel are working titles.
The name of the OS and Kernel are working titles.
January 11, 2026 at 8:00 AM
I fixed it. Not only did I fix it, but it also means I was finally able to implement a shell. What was wrong? Well, I forgot to write the stub for the IRQs like the genius I am so they just weren't being handled at all.
The name of the OS and Kernel are working titles.
The name of the OS and Kernel are working titles.
My neighbour just had their water meter stolen.
I thought a water pipe had burst, but no. Bloody hell.
I thought a water pipe had burst, but no. Bloody hell.
January 9, 2026 at 8:42 AM
My neighbour just had their water meter stolen.
I thought a water pipe had burst, but no. Bloody hell.
I thought a water pipe had burst, but no. Bloody hell.
The screen driver was indeed fucked.
I had the wrong type when trying to access the screen when I should've been using a uint16_t pointer instead.
It works now, though!
I had a bit of a goof where I forgot I told the BL to only load 2 sectors so when kernel.c grew beyond that it triple faulted.
I had the wrong type when trying to access the screen when I should've been using a uint16_t pointer instead.
It works now, though!
I had a bit of a goof where I forgot I told the BL to only load 2 sectors so when kernel.c grew beyond that it triple faulted.
January 9, 2026 at 6:12 AM
The screen driver was indeed fucked.
I had the wrong type when trying to access the screen when I should've been using a uint16_t pointer instead.
It works now, though!
I had a bit of a goof where I forgot I told the BL to only load 2 sectors so when kernel.c grew beyond that it triple faulted.
I had the wrong type when trying to access the screen when I should've been using a uint16_t pointer instead.
It works now, though!
I had a bit of a goof where I forgot I told the BL to only load 2 sectors so when kernel.c grew beyond that it triple faulted.
I got my hobby OS to boot today. It's super basic, the kernel only has print functions, and for some reason it only prints a total of two characters total before catching fire, but hey.
January 8, 2026 at 11:53 PM
I got my hobby OS to boot today. It's super basic, the kernel only has print functions, and for some reason it only prints a total of two characters total before catching fire, but hey.
Found and powered up my old Ti-89 Titanium, hehe.
January 5, 2026 at 10:08 PM
Found and powered up my old Ti-89 Titanium, hehe.
Here's what the moon looked like last night by the way.
January 1, 2026 at 7:05 PM
Here's what the moon looked like last night by the way.
Yeah, just from the error messages I think that's a sign it's just gone. Uuuuughhdhdhhfg
December 27, 2025 at 8:08 AM
Yeah, just from the error messages I think that's a sign it's just gone. Uuuuughhdhdhhfg
When I see bugfixes like these I question NVIDIA's priorities. Though, there's a lot to question either way.
We're talking 2006-2008 CPUs, you have the time to fix this shit yet you're dropping support for the whole GTX 1000 line?
We're talking 2006-2008 CPUs, you have the time to fix this shit yet you're dropping support for the whole GTX 1000 line?
December 18, 2025 at 6:34 PM
When I see bugfixes like these I question NVIDIA's priorities. Though, there's a lot to question either way.
We're talking 2006-2008 CPUs, you have the time to fix this shit yet you're dropping support for the whole GTX 1000 line?
We're talking 2006-2008 CPUs, you have the time to fix this shit yet you're dropping support for the whole GTX 1000 line?
Yeah, this looks about right, been enjoying Nightreign quite a bit.
December 16, 2025 at 9:17 PM
Yeah, this looks about right, been enjoying Nightreign quite a bit.
Okay, I'm having fun again. Damn. Haha.
December 16, 2025 at 4:20 AM
Okay, I'm having fun again. Damn. Haha.
This new plane in Nuclear Option is so very fun to use.
December 16, 2025 at 4:02 AM
This new plane in Nuclear Option is so very fun to use.
I will say, the lights are kind of a vibe, I guess.
December 16, 2025 at 3:15 AM
I will say, the lights are kind of a vibe, I guess.
My school doesn't provide Student IDs, unfortunately.
And I did go to GitHub Support, but I was met with this. It seems I can still send in a ticket regardless? I just might, but y'know.
And I did go to GitHub Support, but I was met with this. It seems I can still send in a ticket regardless? I just might, but y'know.
November 30, 2025 at 4:58 AM
My school doesn't provide Student IDs, unfortunately.
And I did go to GitHub Support, but I was met with this. It seems I can still send in a ticket regardless? I just might, but y'know.
And I did go to GitHub Support, but I was met with this. It seems I can still send in a ticket regardless? I just might, but y'know.
Here's proof that I tried.
November 30, 2025 at 4:41 AM
Here's proof that I tried.