@lyse They say, 18:48 today is the next time slot: https://social.bund.de/@dlr_next/113859521382441187
@lyse They say, 18:48 today is the next time slot: https://social.bund.de/@dlr_next/113859521382441187
@lyse They say, 18:48 today is the next time slot: https://social.bund.de/@dlr_next/113859521382441187
@lyse They say, 18:48 today is the next time slot: https://social.bund.de/@dlr_next/113859521382441187
[](https://movq.de/v/6b6bdafb7e/iss.ff.jpg)
Jupiter and its moons a few days ago:
[](https://movq.de/v/6b6bdafb7e/jupiter.ff.jpg)
Not spectacular shots, but hey, it’s something.
Also saw the crescent Venus and Saturn’s rings through my scope (you know, the one for bird watching).
[](https://movq.de/v/6b6bdafb7e/iss.ff.jpg)
Jupiter and its moons a few days ago:
[](https://movq.de/v/6b6bdafb7e/jupiter.ff.jpg)
Not spectacular shots, but hey, it’s something.
Also saw the crescent Venus and Saturn’s rings through my scope (you know, the one for bird watching).
[](https://movq.de/v/6b6bdafb7e/iss.ff.jpg)
Jupiter and its moons a few days ago:
[](https://movq.de/v/6b6bdafb7e/jupiter.ff.jpg)
Not spectacular shots, but hey, it’s something.
Also saw the crescent Venus and Saturn’s rings through my scope (you know, the one for bird watching).
[](https://movq.de/v/6b6bdafb7e/iss.ff.jpg)
Jupiter and its moons a few days ago:
[](https://movq.de/v/6b6bdafb7e/jupiter.ff.jpg)
Not spectacular shots, but hey, it’s something.
Also saw the crescent Venus and Saturn’s rings through my scope (you know, the one for bird watching).
> Maybe with the very simplest of the easy ones it might be still reasonably straight forward
I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
> Maybe with the very simplest of the easy ones it might be still reasonably straight forward
I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
> Maybe with the very simplest of the easy ones it might be still reasonably straight forward
I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
> Maybe with the very simplest of the easy ones it might be still reasonably straight forward
I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
Corporate IT environments are just a nightmare. Bah. No. We don’t talk about that now. It’s the weekend! 🥳🥳🥳
Corporate IT environments are just a nightmare. Bah. No. We don’t talk about that now. It’s the weekend! 🥳🥳🥳
Corporate IT environments are just a nightmare. Bah. No. We don’t talk about that now. It’s the weekend! 🥳🥳🥳
Corporate IT environments are just a nightmare. Bah. No. We don’t talk about that now. It’s the weekend! 🥳🥳🥳
This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃