summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHombreLaser <buran@silosneeded.com>2025-04-12 23:07:11 -0600
committerHombreLaser <buran@silosneeded.com>2025-04-12 23:07:11 -0600
commit7411607965c031cecdfaf85ac155e3a795f7b345 (patch)
tree76e9dc3260e66b608cfafd9a2cef016a83cf957d
parent31c0d30b4ae6da18a77579a14250d24eea244579 (diff)
I didn't realize I use well too much
-rw-r--r--_posts/en/2025-04-12-picoshock_devlog_2.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/_posts/en/2025-04-12-picoshock_devlog_2.md b/_posts/en/2025-04-12-picoshock_devlog_2.md
index 0a35c91..1b25db5 100644
--- a/_posts/en/2025-04-12-picoshock_devlog_2.md
+++ b/_posts/en/2025-04-12-picoshock_devlog_2.md
@@ -181,13 +181,13 @@ Well, now I have access to a data bus, now I'm actually reading a byte, let's se
# etc...
```
-Well, that's an interesting number. More interesting than 800000, that's for sure.
+That's an interesting number. More interesting than 800000, that's for sure.
Let's write this number in binary:
`0000 0001 0000 0000 0000 0000 0000 0000`
Huh. Interesting... We're waiting a 1, this is by no means a one... but, if we shift it 24 bits to the
-right... it is. So I told myself, well, I'm getting a 1, sort of. If I send data to the PS2 and if when
+right... it is. So I told myself, I'm getting a 1, sort of. If I send data to the PS2 and if when
shifting its responses 24 bits to the right we get the numbers we're expecting... that would
mean I'm now getting the right numbers from the PS2, So that's what we're going to do:
@@ -223,7 +223,7 @@ loop. And it's nothing that scrolling the terminal up can't fix.
![Minicom screenshot](/assets/images/2025/minicom_2.png)
-Well... those numbers seem pretty familiar. According to the [Curious Inventor guide](https://store.curiousinventor.com/guides/PS2),
+Those numbers seem pretty familiar. According to the [Curious Inventor guide](https://store.curiousinventor.com/guides/PS2),
this back and forth communication with the PS2 should look like this:
|Byte # | 1| 2| 3| 4| 5|
@@ -232,9 +232,9 @@ this back and forth communication with the PS2 should look like this:
|-------|----|----|----|----|----|
|Data |0xff|0x41|0x5a|0xff|0xff|
-Well, minus the last 2 data bytes which we're not sending (we're matching 0x00 with 0x5a) all of the command bytes are exactly these,
-when shifted 24 bits to the right, of course. This means that everything I read from the RX FIFO must be shifted 24 bits to the
-right, no biggie.
+Actually, minus the last 2 data bytes which we're not sending (we're matching 0x00 with 0x5a) all of the command bytes are
+exactly these, when shifted 24 bits to the right, of course. This means that everything I read from the RX FIFO must be shifted
+24 bits to the right, no biggie.
-Well, I'm pretty stoked. And this means that now comes the boring part: parsing all those bytes and sending appropriate responses.
-So exciting.
+After all this, I'm pretty stoked. And this means that now comes the boring part: parsing all those bytes and sending appropriate
+responses. So exciting.