elderK has quit [Quit: Connection closed for inactivity]
gabi-250_ has quit [Ping timeout: 240 seconds]
gabi-250_ has joined #osdev
theruran has quit [Quit: Connection closed for inactivity]
gxt has quit [Remote host closed the connection]
vdamewood has joined #osdev
gxt has joined #osdev
yoO0Oo has joined #osdev
yo0O0o has quit [Ping timeout: 260 seconds]
<geist>
well, also propbably because i took some unisom last night, which probably just left me extra groggy today
<geist>
i really shouldnt
<kazinsal>
yeah my sleep schedule is still messed up from the holidays
<kazinsal>
I end up taking a nap around noon and then whoops it's 3pm
<kazinsal>
followed by not falling asleep until 4am and then needing another nap around noon, and...
<FireFly>
same
<geist>
yep, i’m trapped in that right now, going to be hard to crawl out of it
<geist>
as i get older my body is much more stubborn about trying to forcibly move my sleep schedule
<geist>
also more likely to get jet lagged after a long flight
<FireFly>
I think I thrive more with this sleep schedule; it's a pity it's less world-compatible
<kazinsal>
likewise. my optimal sleep schedule is only world-compatible if I happened to live in eastern Australia
<kazinsal>
not so good for someone who lives in the PNW
<FireFly>
and if you did, you would probably have a different optimal sleep schedule :p
<FireFly>
but on that note, I probably ought to try to get some sleep
<FireFly>
I decided to set an alarm tomorrow to nudge myself to not sleep in too hard
<ramenu>
So i'm trying to enter vm86 mode but i'm unsure what im supposed to set the segment registers to. I've tried searching this up for a day or so without luck. I'd appreciate any help or resources i can look at related to this issue
<Mutabah>
You set them like it's 16-bit real-mode
<Mutabah>
(after vm86 mode is entered)
<Mutabah>
in that short period between entering vm86 mode and setting the segment registers, the previous base/limit are still there
<geist>
yeah, though i haven’t checked. how does it context switch back? uses the TSS?
<Mutabah>
TSS
<geist>
TSS boom
<Mutabah>
TSS provides SS/ESP, and the IDT provides CS/EIP
<Mutabah>
then first thing you do (... same as a normal user-kernel switch) is set the rest of the segment selectors
<heat>
find someone that loves you the way intel loves descriptors
<Mutabah>
stacks of legacy
xenos1984 has quit [Read error: Connection reset by peer]
navi has quit [Quit: WeeChat 4.0.4]
<ramenu>
I meant right before entering vm86, when performing iret and pushing the segment registers on the stack
goliath has quit [Quit: SIGSEGV]
xenos1984 has joined #osdev
<Mutabah>
Keep them as-is, you set them once in there
<Mutabah>
Your entry to vm86 mode should be via a stub taht sets up the rest of the user state
<ramenu>
oh ok, thanks
heat has quit [Remote host closed the connection]
heat has joined #osdev
ramenu has quit [Remote host closed the connection]
<bslsk05>
subsurface/subsurface - This is the official upstream of the Subsurface divelog program (502 forks/2508 stargazers/GPL-2.0)
goliath has quit [Quit: SIGSEGV]
<Ermine>
oh lol
vinc has joined #osdev
<Ermine>
Meanwhile I've started looking at tty code, it seems to be more C-styled
<heat>
yep it's almost a straight conversion from C
frkzoid has quit [Ping timeout: 256 seconds]
vinc has quit [Read error: Connection reset by peer]
<Ermine>
While at it: vi works poorly. Is it because some stuff is not implemented in tty or something else?
<Ermine>
And what FDs also need read_iter/write_iter ?
<heat>
vi works poorly and im not sure if its the vterm's fault or the actual vi implementation (comes from toybox, but it's in the 'pending' toys IIRC)
<heat>
things tend to work fine when using a serial terminal
<heat>
but i'm never using vi anyway
theruran has joined #osdev
<Ermine>
Well, there are no other text editors on the image
<heat>
and, erm, technically all FDs need read_iter support
<heat>
like, sockets is probably the big one remaining
<heat>
yeah, nano needs onyx-package-tree
<Ermine>
fifos seem to reuse pipe code interally
<heat>
yeah fifos are pipes
<heat>
i remember now, nano's scrolling is borked
<mjg>
keep it broken
<mjg>
who tf uses nano
<mjg>
you want that on your system
<mjg>
?
<heat>
yeah GNU nano ftw
ramenu has quit [Ping timeout: 268 seconds]
* mjg
moves heat from internet friend list to trashcan
<mjg>
wait did i make it public?
<heat>
Ermine, sockets should be pretty simple, the protocols only implement recvmsg() and sendmsg(), and those take iovecs
<heat>
mjg, you're on my gnuplot users list
<Ermine>
Also, on console it types ? instead of _ and ' instead of - a. Keymap issue?
<heat>
yeah it's a PT layout
<kof123>
next had a blackhole originally, so you could patch the recycle bin graphic in later versions to restore the glorious spinning black hole :D
<heat>
Ermine, if you go to kernel/tty/vt/vterm.cpp:1569 and replace pt_pt_key_actions with key_actions you *should* get a US layout
<heat>
if that helps
<heat>
i don't have a way to dynamically load keyboard layouts yet
freakazoid332 has joined #osdev
<heat>
mjg, fwiw i'm slowly getting more used to vim
<heat>
still, nano is a nice editor
<heat>
easy to use
<heat>
nano requirements: 1) have you used your arrow keys before? 2) can you press keys at all? 3) (CHALLENGING) can you press ctrl+x?
<mjg>
vim is a piece of shit
<mjg>
i would not bother
<heat>
are you an emacs user
<mjg>
no
<heat>
ed?
<mjg>
i use vim, but this is more of inertia
<mjg>
it's a shite editor
<heat>
well yeah
<mjg>
don't go there
<heat>
all UNIX software requires 50 trillion plugins to work properly
<heat>
it's The UNIX Philosophy
<Ermine>
I used nano before, but now I'm too used to vim
<mjg>
is it unix if it's handy?
epony has joined #osdev
<kof123>
hmm....unity of opposites. vi (pronounced six of course) started light for modem links. i use vim, but i don't think it is productive to trick it out. it is only because it was so bare that it could have/need plugins. the historic reason to learn vi is just it would be on nearly every unix system by default