<heat>
i drank a nice freedom beer watching the fireworks
<heat>
it was warm
<heat>
don't care, still worth it
<zid>
how warm
<mjg>
warm gasless beer is portugal's natorional beverage
<mjg>
national
<zid>
americans think anything above -20C is warm beer so it's hard to judge
<heat>
room temperature beer
<zid>
yea fine by me
<mjg>
0% alcohol ofc
<zid>
I've always drank cellar beer so room temp is fine too
<zid>
(cus room temp in my house is like +4C to cellar temp)
<zid>
There, now I have an tbenty fipth abril beertoo
<heat>
i'd shoot myself if i had to drink warm gasless 0% alcohol beer
<zid>
who's drinking that
<heat>
mjg
<zid>
I have a pint of bitter, a real lady's drink
<mjg>
i thought that's what you got legally entitled to after turning 18
<zid>
I wonder if there are videos on youtube of americans trying bitter
<zid>
doesn't really look like it
gog has quit [Read error: Connection reset by peer]
gog has joined #osdev
<zid>
heat: good shout, enjoying my beer
<heat>
you're welcome
<heat>
i hope it's warm and 0% alcohol
<mjg>
see that;s an example of a PESSIMAL beer
<zid>
it was warm, but it's sadly... 3.%
<zid>
3.6%
<zid>
tis a session bitter
<zid>
very smooth
Arthuria has joined #osdev
<nikolapdp>
oh dang, i missed another cpu discussion
<zid>
We came to the conclusion that yu should buy me a W-1390P
<heat>
zid can't get a W
<nikolapdp>
lol
<zid>
W-1390P was my dream cpu a few years ago
<zid>
total paper release though as usual from intel
<nikolapdp>
does it exist at all
<zid>
yea
<zid>
eventually it did come out, in small numbers
<nikolapdp>
that's something at least
<zid>
There's two on ebay, double the retail price
<zid>
nikolapdp do they have beer in serbia
<heat>
yes, it's grey
<heat>
as everything in serbia is
<zid>
they have electricity AND beer? geez
<zid>
I need to re-evaluate
<nikolapdp>
zid: yes we do
<nikolapdp>
heat: no, that's russia
<nikolapdp>
plus, electricity is cheap
<heat>
what colour is serbia?
<nikolapdp>
depends on the glowin orb in the sky
<heat>
light grey or dark grey, got it
volum has quit [Quit: Client closed]
gog has quit [Ping timeout: 268 seconds]
goliath has quit [Quit: SIGSEGV]
Arthuria has quit [Ping timeout: 245 seconds]
raykv423 has quit [Quit: Connection closed for inactivity]
xenos1984 has quit [Read error: Connection reset by peer]
JerryXiao has quit [Ping timeout: 255 seconds]
JerryXiao has joined #osdev
volum has joined #osdev
xenos1984 has joined #osdev
volum has quit [Quit: Client closed]
volum has joined #osdev
hmw[at] has quit [Ping timeout: 245 seconds]
arminweigl has quit [Ping timeout: 256 seconds]
arminweigl has joined #osdev
Matt|home has joined #osdev
hmw[at] has joined #osdev
\Test_User has quit [Quit: .]
<heat>
geist, does qemu emulate baud rates for serial ports?
\Test_User has joined #osdev
Arthuria has joined #osdev
alpha2023 has quit [Ping timeout: 260 seconds]
alpha2023 has joined #osdev
hunta987 has quit [Quit: Lost terminal]
volum has quit [Quit: Client closed]
vdamewood has joined #osdev
volum has joined #osdev
<geist>
AFAIK it doesn't
<geist>
there's no rate limiting on it
Arthuria has quit [Killed (NickServ (GHOST command used by Guest684531))]
<geist>
that can actually be a problem if you're not careful when writing a uart RX IRQ handler for your system
<geist>
if you dump a lot of data into qemu at once, and your irq handler has a big infinite loop that handles characters as they come in, it can basically sit in IRQ mode indefinitely
<geist>
in the real world this doesn't happen unless the cpu is super slow, since serial speed is nothing compared to the cpu
heat has quit [Ping timeout: 240 seconds]
<kazinsal>
ran into a similar issue with vbox back in the day
khrbtxyz has joined #osdev
khrbtxyz has quit [Remote host closed the connection]
khrbtxyz has joined #osdev
khrbtxyz has quit [Remote host closed the connection]
freakazoid332 has quit [Ping timeout: 260 seconds]
carbonfiber has quit [Quit: Connection closed for inactivity]
FireFly has quit [Ping timeout: 255 seconds]
volum has quit [Quit: Client closed]
frkazoid333 has joined #osdev
d5k has joined #osdev
randm has quit [Read error: Connection reset by peer]
randm has joined #osdev
wantyapps has quit [Remote host closed the connection]
wantyapps has joined #osdev
d5k has quit [Ping timeout: 256 seconds]
zetef has joined #osdev
tjf has quit [Ping timeout: 260 seconds]
fluix has quit [Ping timeout: 256 seconds]
rwb has joined #osdev
rb has quit [Ping timeout: 256 seconds]
fluix has joined #osdev
rwb is now known as rb
tjf has joined #osdev
volum has joined #osdev
carbonfiber has joined #osdev
zetef has quit [Remote host closed the connection]
neo has quit [Remote host closed the connection]
neo has joined #osdev
khrbtxyz has joined #osdev
gbowne1 has quit [Quit: Leaving]
zetef has joined #osdev
zetef has quit [Remote host closed the connection]
spareproject has joined #osdev
neo has quit [Read error: Connection reset by peer]
volum has quit [Ping timeout: 250 seconds]
GeDaMo has joined #osdev
clever has quit [Ping timeout: 240 seconds]
volum has joined #osdev
clever has joined #osdev
navi has joined #osdev
rorx has quit [Ping timeout: 256 seconds]
gog has joined #osdev
navi has quit [Read error: Connection reset by peer]
navi has joined #osdev
carbonfiber has quit [Quit: Connection closed for inactivity]
FireFly has joined #osdev
Left_Turn has joined #osdev
leg7 has joined #osdev
leg7 has quit [Remote host closed the connection]
leg7 has joined #osdev
<ddevault>
the integration workload with respect to lwext4 is non-trivial (given that I am not using their silly "mountpoint" abstraction), but hey, I get a good filesystem on the cheap so I'll take it
leg7 has quit [Remote host closed the connection]
<kazinsal>
never seen lwext4 before. putting that on the to-do list
<kazinsal>
whipping up an ext2 driver is quick and easy but I definitely want journaling
<kazinsal>
might make it a challenge to myself to rewrite the xattr bits as BSD licensed
xenos1984 has quit [Read error: Connection reset by peer]
leg7 has joined #osdev
<leg7>
hello I'm reading the documentation of multiboot 0.6.69 and I think I've found a mistake in the example code they give and I would like to know what you think. They do #define MULTIBOOT_MEMORY_INFO 0x00000002 which would set bit 1 (0 indexed) of the flags. but bit 1 doesn't represent memory info but the boot device. Then #define MULTIBOOT_INFO_MEMORY 0x00000001 is declared a bit lower this time with a slightly different name but a correct value.
<bslsk05>
www.gnu.org: Multiboot Specification version 0.6.96
xenos1984 has joined #osdev
<kazinsal>
the flags you pass in your multiboot header are not the same layout as the flags that you get back in `struct multiboot_info`
<leg7>
ok
<kazinsal>
`MULTIBOOT_MEMORY_INFO` is for what you pass in your header
<kazinsal>
you pass a flags with bit 1 set, and the multiboot loader sets bit 0 in the `multiboot_info` flags to say that the memory map fields are valid
<leg7>
yeah I got it ty
<leg7>
one more thing. They define // Alignment of multiboot modules. #define MULTIBOOT_MOD_ALIGN 0x00001000; // Alignment of the multiboot info structure. #define MULTIBOOT_INFO_ALIGN 0x00000004
<leg7>
for the input structure but I can't find these flags documented anywhere
volum has quit [Quit: Client closed]
<leg7>
In section 3.1.2 only bits 0, 1, 2, and 16 are documented
<kazinsal>
`MULTIBOOT_MOD_ALIGN` isn't a flag, it's the physical memory alignment of loaded modules if `MULTIBOOT_PAGE_ALIGN` is set
<kazinsal>
similarly `MULTIBOOT_INFO_ALIGN` is the physical memory alignment of `struct multiboot_info`
<leg7>
oh k
<leg7>
tyty
<kazinsal>
so `struct multiboot_info` will always be aligned on a 4-byte boundary, and if `MULTIBOOT_PAGE_ALIGN` is set in your request flags, all modules will be aligned on 4KiB page boundaries
<leg7>
yeah thanks
<leg7>
have a nice day o/
leg7 has quit [Remote host closed the connection]
netbsduser has joined #osdev
<zid>
It puts the comments in the code or it gets the hose
netbsduser has quit [Ping timeout: 264 seconds]
Matt|home has quit [Quit: Leaving]
volum has joined #osdev
m257 has joined #osdev
Arthuria has joined #osdev
zetef has joined #osdev
Beato has quit [Remote host closed the connection]
edr has joined #osdev
Beato has joined #osdev
Arthuria has quit [Ping timeout: 268 seconds]
bauen1 has quit [Ping timeout: 252 seconds]
volum has quit [Quit: Client closed]
bauen1 has joined #osdev
night_ has quit [Quit: No Ping reply in 180 seconds.]
zetef has quit [Remote host closed the connection]
night has joined #osdev
<nikolapdp>
a server at work: up 1637 days
<zid>
not bad, couple days longer than my desktop
<mjg>
bragging about high uptime is high schooler's first unix
<mjg>
you are supposed to grow out of it
<mjg>
in fact high uptime mostly shows you are running an unpatched kernel
<mjg>
and that things may not even get up after a reboot
<nikolapdp>
i know, it wasn't a brag
<nikolapdp>
i am finally about to update it
<mjg>
mon
<mjg>
dafaq you doin not bragging
<nikolapdp>
what's the opposite of bragging
heat has joined #osdev
<mjg>
nikolapdp: i don't know, boomering?
<heat>
huh does kexec reset the uptime?
<clever>
i would expect it to reset uptime
<gog>
zid: just beat black stake
<gog>
blue deck
<gog>
found the 5x mult joker
<gog>
yorick
<gog>
oh blue stake
<heat>
hey gog you should get addicted to gambling
<heat>
it's a great idea
<heat>
much better than pretend poker
<heat>
don't forget, you can stop whenever you want
<gog>
ok
<heat>
damn i'm persuasive
<nikolapdp>
lol
Maja has quit [Quit: No Ping reply in 180 seconds.]
Maja has joined #osdev
vdamewood has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
heat_ has quit [Read error: Connection reset by peer]
heat_ has joined #osdev
goliath has joined #osdev
gbowne1 has joined #osdev
spareproject has joined #osdev
foudfou has quit [Remote host closed the connection]
foudfou has joined #osdev
masoudd has joined #osdev
Rubikoid has quit [Read error: Connection reset by peer]
Rubikoid has joined #osdev
* childlikempress
waits expectantly
<zid>
childlikempress: Hold your breath for me a sec
<zid>
I'll tell you when to exhale
goliath has quit [Quit: SIGSEGV]
<vin>
I might have asked this question before (but failed to document it) so please bear with me. Is there a historical significance about why page/block size is 4KB and which system started using it first?
k_hachig has quit [Ping timeout: 256 seconds]
<heat_>
geist, have you thought of just building your lkuser on the first magenta commit?
<heat_>
was just looking at it, it's super lk-like still :D
<heat_>
and docs literally mention an lkuser (which doesn't seem to be present)
GeDaMo has quit [Quit: That's it, you people have stood in my way long enough! I'm going to clown college!]
heat_ has quit [Remote host closed the connection]
heat_ has joined #osdev
<heat_>
huh this was fairly monolithic
goliath has joined #osdev
<heat_>
drivers, in the kernel, in C
<heat_>
mega based
<zid>
whoa crazy idea
<heat_>
ikr
<heat_>
shame they abandoned this crazy idea
<heat_>
had potential
qubasa has joined #osdev
spareproject has quit [Remote host closed the connection]
xenos1984 has quit [Read error: Connection reset by peer]
heat has joined #osdev
heat_ has quit [Read error: Connection reset by peer]
xenos1984 has joined #osdev
<netbsduser>
until i saw the kernel/lib/magenta directory in it i thought it was almost entirely just little kernel
<netbsduser>
with only kernel/vm showing serious signs of infestation by the C++ language
Left_Turn has quit [Read error: Connection reset by peer]
<netbsduser>
good grief, i had no idea the magenta libc was really a derivative of muslibc
<heat>
it still is
<heat>
it just got further google'd
<netbsduser>
one thing i will say about C++
<netbsduser>
i threw together a testbed kernel in C++ to test some radical ideas i had for my proper kernel (increasing lock granularity and introducing some lock-free fast paths in synchronisation; RCU: Classic Edition; more robust timers that you can reliably either cancer or wait til completion; sophisticated page replacement)
<heat>
booo no cancer
<netbsduser>
and it was when i began translating the first of those experiments back to C to put in my proper kernel that i realised how virtuous it is that in C++ automatic variables are so powerful with their constructor and destructor
<netbsduser>
i could replace lock acquisitions with a `ScopedLock(some_lock) locked;` and spl calls with `ScopedIpl(kIPLClock) ipl;` and get rid of repeatedly having to call unlock and splx in all return positions
<netbsduser>
a big cleanup
<heat>
it's almost as if C++ isn't all that bad
<heat>
oh no wait C++ is very bad ungood
<zid>
correct.
<heat>
C++ killed my father during vietnam
<zid>
only *my* subset of C++ is useful, heat
<heat>
let me guess
<heat>
that subset is zid c
<zid>
who cares, the important part is that it's DIFFERENT
<nikolapdp>
C C C C C C
<kof673>
CCCCCC VI what is the other 6?
<heat>
i got it to build but its not booting :(
k_hachig has joined #osdev
<netbsduser>
c++ is obviously a very large language and no one really knows it, like people know c
<netbsduser>
but the large stuff is also nice
<heat>
people know C??
<netbsduser>
i moved to profoundly asynchronous I/O but i need a thread pool to do FS I/O because i do have a continuation-based monster framework but i am NOT writing an FS driver against that, it's too much
<gog>
i don't know C
<netbsduser>
while managarm by contrast uses C++ asyncroutines which lets them do it without writing synchronous code and making it "async" by running it in aworker thread as i have to
<childlikempress>
i knew c once
<childlikempress>
thankfully i've recovered
<MrBonkers>
Managarm seen, ping received :^)
<heat>
MANAGARM MLIBC
<heat>
you should have your client ping on "profoundly asynchronous I/O" too
heat has quit [Remote host closed the connection]
<childlikempress>
i will never synchronise
<childlikempress>
synchronisation is for cowards
heat has joined #osdev
<acidx>
*** heat has quit (Coroutine yielded and immediately killed from profoundly asynchronous I/O loop)