<FireFly>
yeah, I remember the default homebrew template basically has a shim that reads the controllers/etc and sets it in memory the arm9 core can read, for the arm7 program
<zid>
FireFly: Funner fact, one of the main names in the DS scene is firefly
<zid>
or rather, was, 20 years ago..
<FireFly>
yes, I remember running into their work back when I looked into it maybe 15 years ago, which was confusing :p
<immibis>
i tried to make an N64 emulator for DS, not knowing much about emulation or the N64. That failed, but it was a very fun project
<zid>
They wrote the modified rt2560 driver that let you talk to the DS from a PC, importantly
<immibis>
they are roughly comparable hardware
<FireFly>
I used to be a fairly avoid consumer of DS homebrew at one point
<FireFly>
good scene
<zid>
(and sgstair who I am still friends with, wrote the ds side wifi library)
<immibis>
casual reminder that the DS era was before the smartphone era.
<immibis>
having DS homebrew was having a smartphone before smartphones. No internet though.
<FireFly>
zid: oh TIL, didn't know that part
<FireFly>
... their nick is familiar
<immibis>
other people had MP3 players, you had a multifunction device.
<bslsk05>
www.zachtronics.com: Zachtronics | KOHCTPYKTOP: Engineer of the People
<FireFly>
ah yes
<FireFly>
constructor, that was it
<FireFly>
(but cyrillic)
<FireFly>
I had the right idea :p
<zid>
lastcall bbs has a small version of it
bitoff_ has quit [Ping timeout: 252 seconds]
<zid>
it's not very exciting :(
<zid>
The dungeons and dragons game and its solitaire are fucking rad though
<zid>
I have erm.. 500 wins
netbsduser has quit [Ping timeout: 245 seconds]
rpnx has joined #osdev
vinc has quit [Read error: Connection reset by peer]
bitoff_ has joined #osdev
bitoff__ has quit [Ping timeout: 268 seconds]
PublicWiFi has quit [Quit: WeeChat 4.0.3]
Left_Turn has quit [Ping timeout: 268 seconds]
rorx has quit [Ping timeout: 252 seconds]
<pwng>
Hi all. I have a 2-stage bootloader that does nothing but read 2nd sector to (0x07E0:0x0000, 0x7E00) & attempts to switch to protected mode... i get triple-faults unless I set segment registers to 0 in the second stage... my code is here: https://ideone.com/YRBhGt ... I'd appreciate if someone explains why does this happen :-) (there's a very
<bslsk05>
www.nasm.us: NASM - The Netwide Assembler
<pwng>
Thank you for your response... so i understand why it works (and i can just move on since it works), but do you see any potential issues with having the the segment values of 0? i already switched to protected mode so it's probably fine but just to make sure
<pwng>
segment registers' values*
<pwng>
Mutabah: ^ (i hope this is the proper way to mention someone :D)
<Mutabah>
(Yep, that's how you do it)
<Mutabah>
No issues with setting the segment registers to zero
<Mutabah>
(while in real mode)
<Mutabah>
well, maybe don't set `ss` to zero
<Mutabah>
but `ds` (and the other data regs, but they're not really needed) should be zero for this code
<Mutabah>
once you're in protected mode, you should reset all of them to the data selector anyway
<pwng>
yes, now I understand... many thanks Mutabah
Left_Turn has joined #osdev
Left_Turn has quit [Read error: Connection reset by peer]