klange changed the topic of #osdev to: Operating System Development || Don't ask to ask---just ask! || For 3+ LoC, use a pastebin (for example https://gist.github.com/) || Stats + Old logs: http://osdev-logs.qzx.com New Logs: https://libera.irclog.whitequark.org/osdev || Visit https://wiki.osdev.org and https://forum.osdev.org || Books: https://wiki.osdev.org/Books
elastic_dog has quit [Remote host closed the connection]
elastic_dog has joined #osdev
<bslsk05> ​users.atw.hu: Dawn for SUBLEQ
<heat> i miss this guy
<heat> wonder what happened to him
Burgundy has quit [Ping timeout: 240 seconds]
gog has quit [Quit: byee]
frkazoid333 has quit [Ping timeout: 248 seconds]
<kazinsal> probably realized that gimmick virtual machines are just that
<kazinsal> also appears to have been "funded" by a bunch of crypto shills who are probably now bankrupt
elastic_dog has quit [Ping timeout: 248 seconds]
elastic_dog has joined #osdev
dutch has quit [Quit: WeeChat 3.8]
dutch has joined #osdev
<geist> wow he definitely has a point of view
<geist> omg is this literally one of those stupid one instruction turing machine things?
<kazinsal> yeah
<kazinsal> the comparison of a jpeg library being larger than the apollo guidance computer's code library is one of those things that makes me realize he has no idea what the fuck he's talking about
<geist> right
<geist> i mean i guess grats if he got a gui running on a turing machine, but because the architecture is simple does not make it easy or worthwhile to use
<geist> "look at how simple my unicycle is, since its simple it's intrinsically superior to all other forms of wheeled transportation"
<kazinsal> "-The national surveillance is wired to your ISP. 1 Does not matters, where you live.2" yeah buddy I'm sure that your twenty effective mips gimmick vm is gonna help you with that. might i suggest a carbon monoxide detector instead
pharonix71 has joined #osdev
elastic_dog has quit [Ping timeout: 250 seconds]
elastic_dog has joined #osdev
CalculusCats is now known as CalculusCat
[itchyjunk] has quit [Read error: Connection reset by peer]
pg12 has quit [Ping timeout: 240 seconds]
pg12 has joined #osdev
Arthuria has joined #osdev
osmten has joined #osdev
clever has quit [Ping timeout: 246 seconds]
bradd has joined #osdev
xenos1984 has quit [Quit: Leaving.]
frkzoid has joined #osdev
frkazoid333 has joined #osdev
frkzoid has quit [Ping timeout: 252 seconds]
clever has joined #osdev
xenos1984 has joined #osdev
bgs has joined #osdev
bliminse has quit [Quit: leaving]
clever has quit [Ping timeout: 255 seconds]
pmaz has joined #osdev
wlemuel has quit [Ping timeout: 255 seconds]
wlemuel has joined #osdev
Arthuria has quit [Remote host closed the connection]
bliminse has joined #osdev
bliminse has quit [Client Quit]
bliminse has joined #osdev
linear_cannon has quit [Ping timeout: 248 seconds]
linear_cannon has joined #osdev
slidercrank has joined #osdev
foudfou has quit [Remote host closed the connection]
foudfou has joined #osdev
gildasio1 has quit [Remote host closed the connection]
gildasio1 has joined #osdev
goliath has joined #osdev
Halofreak1990 has quit [Ping timeout: 240 seconds]
heat has quit [Remote host closed the connection]
heat has joined #osdev
Jari-- has joined #osdev
wlemuel has quit [Quit: Ping timeout (120 seconds)]
wlemuel has joined #osdev
eroux has quit [Quit: Textual IRC Client: www.textualapp.com]
clever has joined #osdev
eroux has joined #osdev
eroux has quit [Client Quit]
eroux has joined #osdev
vdamewood has joined #osdev
eroux has quit [Ping timeout: 248 seconds]
eroux has joined #osdev
uddipiggu has quit [Remote host closed the connection]
uddipiggu has joined #osdev
bauen1 has quit [Ping timeout: 240 seconds]
danilogondolfo has joined #osdev
bl4ckb0ne has quit [Changing host]
bl4ckb0ne has joined #osdev
gog has joined #osdev
Jari-- has quit [Ping timeout: 240 seconds]
kspalaiologos has joined #osdev
theboringkid has joined #osdev
GeDaMo has joined #osdev
Burgundy has joined #osdev
kspalaiologos has quit [Ping timeout: 264 seconds]
Ali_A has joined #osdev
xvmt_ has joined #osdev
xvmt_ has quit [Remote host closed the connection]
bauen1 has joined #osdev
xvmt has quit [Read error: Connection reset by peer]
xvmt has joined #osdev
slidercrank has quit [Quit: Why not ask me about Sevastopol's safety protocols?]
osmten has quit [Ping timeout: 260 seconds]
kspalaiologos has joined #osdev
kspalaiologos has quit [Quit: Leaving]
theboringkid has quit [Ping timeout: 240 seconds]
bnchs has joined #osdev
bradd has quit [Ping timeout: 240 seconds]
<kof123> that subleq thing: The compiler requires the following: -A fast (4 GHz or faster) CPU -1 GByte free RAM -1 GByte disk space
* kof123 dies
<kof123> (no idea about the hosted, that is cross-compiler)
nyah has joined #osdev
<gog> 4GHz or faster??
CalculusCat has quit [Quit: Meow meow meow meow meow meow meow...]
<gog> idk if mine even does that
awita has joined #osdev
<gog> max boost clock 4GHz
CalculusCat has joined #osdev
<zid`> I have no idea what my cpu does, it's amd so it's whatever it feels like
<zid`> "idk, something? Maybe more if you cool it harder?"
<zid`> official spec ^
<gog> ryzen ryzen ryzen
<gog> i know i've said it before but i love my ryzen so much
<zid`> AMD AMD AMD
<zid`> Never used an intel cpu in my life
<gog> intel who?
<gog> aren't those the people who hate women?
<zid`> they're some 2-bit cpu company, like cyrix
<gog> oh wow my max temp is 105°C
<zid`> yea but it'll deboost at 95C
<gog> no wonder it's never throttled
<zid`> 105C is the thermal shutdown
<gog> i don't think i've ever broke 75
<gog> my GPU however will sit comfortably at 80
<zid`> laptops are pretty good at hitting that 95C thing if you shock-load them
<zid`> cus power density
<gog> prime95 isn't going to do it anymore i don't think
<gog> i need a different full-load program
<moon-child> $ sysctl dev.cpu|grep temperature|awk '{print $2}'|sort -n|tail -1
<moon-child> 36.0C
<zid`> random sensors pretty useless for "cpu temperature" these days
<zid`> they generate their temp in random hotspots now, so package temp is meh as a measurement
<moon-child> idk there's just one temp measurement for each core
<zid`> that it shows you, and a package temp, and a cache temp
<zid`> there's multiple sensors per core, it does MAX(those) for those core temp
<gog> i think i'd also have to be loading the gpu cores at the same time
<zid`> oh and a per ccd temp
* moon-child laughs in uma
pmaz has quit [Quit: Konversation terminated!]
<zid`> I have a nice cpu with only one ccd though, saves a bunch of numa shit
<moon-child> doesn't that just mean it has only, like, 2 cores
<zid`> 8
<zid`> wtf is PCT0 and UAD0 temp sensor..
<zid`> They're clearly made up, they're stuck at 16.8C
eroux has quit [Read error: Connection reset by peer]
eroux has joined #osdev
bauen1 has quit [Ping timeout: 276 seconds]
CalculusCat is now known as CalculusCats
Ali_A has quit [Quit: Client closed]
awita has quit [Ping timeout: 240 seconds]
warlock has quit [Ping timeout: 240 seconds]
bauen1 has joined #osdev
theboringkid has joined #osdev
theboringkid has quit [Quit: Bye]
vdamewood has quit [Quit: Life beckons]
wereii has quit [Quit: ZNC - https://znc.in]
wereii has joined #osdev
wereii has quit [Quit: ZNC - https://znc.in]
wereii has joined #osdev
<heat> i get 55kloc for a font (univga) with 2900 codepoints :/
<heat> i'm afraid this is too large to get into the kernel by default
<heat> particularly as I get 50+ KiB out of font data
<zid`> compress it
<zid`> have you considered that each line is infact, a macro that declares a byte, which is why you get 50k and 50k? :P
<mjg> ship it
<mjg> not compress
<heat> yes I have considered it
<gog> hi
<heat> but 1) that doesn't help me with runtime size (the 50KiB)
<heat> 2) that doesn't help me if I want to touch it up in the future (unlikely, but...)
<sham1> Leave rendering up to the userland
<heat> no
<heat> i need a kernel console and a kernel font
<GeDaMo> How big are the characters?
<heat> 8x16
<mjg> 2x4
<GeDaMo> 8x8, 5x7 :P
xenos1984 has quit [Quit: Leaving.]
<mjg> 80x24
vdamewood has joined #osdev
wereii has quit [Changing host]
wereii has joined #osdev
<sham1> That's a large character
<sham1> Also no, you don't need a kernel console. You want to have one (for some reason)
[itchyjunk] has joined #osdev
wereii has quit [Quit: ZNC - https://znc.in]
<heat> yes, i need a kernel console, because this is a unix
<zid`> why do you care about 50k btw
<heat> a UNIX system without a kernel console is like a Windows clone without DoThing, DoThingEx, DoThingA, DoThingW, DoThingExA, DoThingExW
<heat> cuz it's large
<zid`> not really?
wereii has joined #osdev
<zid`> it's a 8x50000 bitmap
<sham1> UNIX is when kernel console. But seriously though, if you want to do it then you really have no choice other than to have the font then, which means paying the price with memory usage
<heat> but I already have a font, its just not unicode
<bnchs> heat: i want my KillMyselfExA
<heat> thank you benches, very cool
<sham1> hRope
<mjg> KillMyseflByHandle
<bnchs> microsoft devs be like WriteAVeryLongFunctionNameExplainingWhatTheFunctionDoesExA
<nortti> are there unices that do support more than like 512 codepoints in the kernel console?
<heat> yes, mine
<zid`> mine
<zid`> but it's not a unix
<zid`> 56540 lines (56538 sloc) 830 KB
<zid`> my font
<nortti> what does it cover?
<kof123> i'm total opposite, snake_case_never_uppercase_functions_ever() completely different
<heat> anyway, it's the second largest thing in my kernel. I even have a char_indices that does utf_to_char in the font atm, which is huge (128KiB) but can be removed with some care, just a dirty O(1) char mapping solution
<sham1> I'd make it so that the init process launches a terminal emulator that takes the kernel provided graphics context and draws the thing there. Works fine with a UNIX mode
<heat> nortti, i'm using univga which covers most of the important language stuff of unicode
<sham1> Of course I'm also obsessed with putting things in userspace, so that's a thing
<kof123> flash your bios or uefi splash screen and stick it in there in "rom"
* kof123 runs
<nortti> heat: do you do text shaping in-kernel too?
<heat> not really
<nortti> or, hm, not shaping. but the thing where you select correct context-specific glyph
<nortti> in that case you can eliminate scripts that require that without regression, can't you?
<heat> if you mean doing "a´"->"á", no
<zid`> COMPOSITION
<zid`> dirty practice
<nortti> no I mean like how arabic initial and final forms are different but encoded using the same codepoint
<sham1> INHERITANCE
<sham1> nortti: that would be shaping
<zid`> ligatures?
<zid`> shaping? pfft
<sham1> Kind of like how Greek has a word-final small sigma and a median sigma form
<heat> yeah erm no, i'm not doing anything fancy like that
<nortti> sham1: ah, okay. I thought shaping was the process of adjusting the locations of combining glyphs to make the final glyph
<heat> it works exactly as one would expect from a latin-script centric thing. codepoint gets character in console cell, done
<sham1> That's part of it
<zid`> doesn't really go together with quick bitmap font
<nortti> heat: do you handle halfwidth vs. fullwidth?
<heat> no
<GeDaMo> Are you doing right-to-left text?
<heat> i tested with romanian and russian, and I get good output, so that covers most of europe, and I'm happy
<heat> dawg
<heat> <heat> it works exactly as one would expect from a latin-script centric thing. codepoint gets character in console cell, done
<GeDaMo> Then why have all the codepoints?
<heat> because i can now print russian
<sham1> ^
<sham1> Can you print Ukrainian
<heat> yes
<nortti> heat: I think GeDaMo is asking why you (presumably) include code points for languages that require LTR, like hebrew
<nortti> RTL even
<heat> because i'm taking the bdf font as-is
<heat> and not supporting hebrew, etc is a flaw
<heat> even though I probably won't ever care enough to support it, but who knows
<sham1> Unless you want to add text shaping, you won't be supporting those kinds of languages in a kernel
<heat> there's RTL support in VT100-ish stuff
<nortti> I thought hebrew was pretty simple? does it have context-dependant forms too?
<nortti> okay, unicode seems to encode those forms as separate codepoints
<bslsk05> ​learn.microsoft.com: Developing OpenType Fonts for Hebrew Script - Typography | Microsoft Learn
<nortti> ah, right, pointing
<Ermine> Are you people talking about supporting RTL languages in consoles (e.g. without GUI)?
<nortti> specifically as part of the system console, and not as normal userland application
<zid`> I'm sure there are norms for printing fucked up langs using bad fonts
<zid`> hell, japanese uses yen as the fucking path sep because the console font doesn't have \
<zid`> or keyboard
<nortti> it's a bit more complex than that. the japanese national variant of ASCII reassigned the codepoint where \ is (as it was national use codepoint) to ¥
<zid`> yup
<zid`> It's a good example of "guess we'll make do" when you're limited by encodings/fonts/etc though
<nortti> aye, plus backcompat
<heat> "hell, japanese uses yen as the fucking path sep" LOL
<nortti> windows is natively unicode so they could have just separeted \ and ¥ like how mac os x does
<nortti> but ppl are used to ¥ and \ being the same so they are
<zid`> I am used to typing dates wrong into american software, similarly.
linearcannon has joined #osdev
linear_cannon has quit [Ping timeout: 255 seconds]
awita has joined #osdev
wlemuel has quit [Quit: Ping timeout (120 seconds)]
wlemuel has joined #osdev
dude12312414 has joined #osdev
ornx has quit [Ping timeout: 255 seconds]
ornx has joined #osdev
heat has quit [Remote host closed the connection]
heat has joined #osdev
awita has quit [Remote host closed the connection]
<ddevault> has anyone had success in setting up GNU-EFI or POSIX-UEFI here
<heat> yes
<ddevault> which?
<heat> gnu efi
<ddevault> is it halfway decent
<heat> yeah I guess. what are you looking for?
<ddevault> want to write an x86_64 EFI bootloader in C
<heat> oh that's perfect for gnu-efi then
<ddevault> cool
<ddevault> will give it a go
<bslsk05> ​github.com: Carbon/Makefile at master · heatd/Carbon · GitHub
<heat> keep in mind that gnu-efi's path may change from distro to distro. I haven't found a solution just yet, maybe there's a pkgconfig thing somewhere
<ddevault> I don't have a pc file
<ddevault> ¯\_(ツ)_/¯
<ddevault> do you recommend using mingw, clang, or objcopy to produce PE files
<zid`> hex editor
<zid`> nothing else can be trusted
<heat> objcopy
<ddevault> I will be a happy man if I never look at a hexdump of a PE file again
<heat> so, erm, if you use mingw or clang in windows-pe mode you don't really need gnu-efi
<ddevault> err good point
<heat> cuz basically the really crucial and hard-to-get bit in gnu-efi is relocation processing
<heat> because objcopy doesn't convert those for you, so its crt0.o does the ELF reloc processing as your PE file will have 0 relocs
<ddevault> yeah
<bslsk05> ​wiki.osdev.org: UEFI App Bare Bones - OSDev Wiki
<ddevault> this approach seems okay enough
<ddevault> with mingw or clang
<ddevault> and gnu-efi just for headers and uuids
<heat> if you're not using gnu-efi for its crt0 I would just crib fuchsia's efi headers
* ddevault looks for it
<heat> cuz MIT licensed and easy enough to remove from the project, and you don't need to deal with extra 3rd party libs
<ddevault> is it going to be full of C++ junk
<ddevault> headers are more or less uncopyrightable imho
<heat> no
<ddevault> ditto for lists of guids
<bslsk05> ​fuchsia.googlesource.com: zircon/kernel/lib/efi/include/efi - fuchsia - Git at Google
<ddevault> oh this is pretty decent
<ddevault> thanks
<heat> I took them (https://github.com/heatd/Onyx/tree/master/kernel/include/efi) and re-EfiStyle'd them because of my stockholm syndrome
<bslsk05> ​github.com: Onyx/kernel/include/efi at master · heatd/Onyx · GitHub
<heat> no problem
<bslsk05> ​github.com: sophia/api/efi at main · adachristine/sophia · GitHub
<gog> my headers are best
<gog> the are public domain
<heat> >#pragma once
<ddevault> >whoever is outside my house yelling "comment your code!" i will never comment my code
<heat> heretic!!!!!1111!!!!!1111!!!!!11
<ddevault> we can be friends, gog
<gog> pragma once is superior
<gog> ddevault: :D
<ddevault> >#pragma once
<ddevault> we cannot be friends
<gog> lol
<gog> get with the times nerds
<gog> header guards are for failed preprocessors
<heat> your mom is a failed preprocessor
<gog> i know
<heat> #pragma once is for LOOOSERS who don't care about PORTABILITY to K&R C COMPILERS
<ddevault> mfw I'm going to incorporate Fuschia code into my system
<heat> fuchsia*
<ddevault> the number of things I swore I would not do and ended up doing anyway is rather high so far this year
<ddevault> I'm learning french for fuck's sake
<gog> if you care about K&R C compilers you should begin looking for a good retirement home
<gog> leave your rotting code to die
<heat> no
<heat> kr compiler best
<mjg> performance showdown
<mjg> there is a folklore story how unix got ported to some not-pdp11
<mjg> but they did not have an optimizing ocmiler for the cpu
<mjg> yet nobody complained aboutp erformanc
<mjg> e
<mjg> conclusion: write sensible code and it will already be fast1111
<mjg> lol
<heat> i'm fairly sure I wouldn't notice it much if I accidentally -O0'd everything
<kof123> eh, i will use pragma to generate headers ...k&r is likely too much for me but ...
<ddevault> -O doesn't make your code fast
<ddevault> writing fast code makes your code fast
<kof123> *generate guards
<ddevault> exception: SSE
<kof123> but other things too
<kof123> even i have my limits of how far i will cripple code
<heat> oh, it would definitely have a difference
<heat> but in human scale? probably not
<heat> you can sanely run ASAN+UBSAN builds on lots of software without realising it, including the kernel
<heat> in my experience it's only really noticeable when you're doing a lot of data moving (drawing to a framebuffer, decompressing)
<mjg> i already noted people only know somethign is slow when it visible tears on the screen
<mjg> or they happen check what's going on
<mjg> happen to*
<mjg> ffs
<heat> yep, 100%
<heat> i should get a flamegraph to see why my kernel console sucks, shouldn't I
<mjg> it does?
<heat> it's slow
<mjg> have you tried not using an optimizing compiler :X
<gog> have you tried not having a console
<heat> the general strategy I use for scrolling sucks, I think
<mjg> you literally emean console
<mjg> or terminal emulation in general
<gog> never scroll
<gog> just roll to the top
<mjg> buy a bigger monitor
<heat> mjg, vt
bnchs has quit [Remote host closed the connection]
<mjg> there is your mistake
<mjg> is it slower than vt100
<zid`> Use a display device that supports wrapping
<zid`> then performance is freeee
<GeDaMo> Teletype! :P
<mjg> zero cost abstraction
<zid`> You write a row out, then adjust scroll reg +8, done
<zid`> also tearing free
<ddevault> blink the backlight in morse code
<ddevault> fewer lines of code means more performance and less bugs
<bslsk05> ​'Using a 1930 Teletype as a Linux Terminal' by CuriousMarc (00:16:33)
<mjg> + /* swap using fast memcpy() */
<mjg> + memcpy(tmp, pa, es);
<mjg> + memcpy(pa, pb, es);
<mjg> + memcpy(pb, tmp, es);
* mjg has doubts
Halofreak1990 has joined #osdev
<heat> oh gawd
<heat> i mean, I guess
<heat> if es is const or const-ish the compiler should be able to make that into loads/stores
<zid`> why can they not use =
<heat> or possibly a swap too
Halofreak1990 has quit [Ping timeout: 248 seconds]
Halofreak1990 has joined #osdev
FreeFull has joined #osdev
slidercrank has joined #osdev
* sham1 looks at scrollback
<sham1> #pragma once forever
<sham1> I'd love for there to be a more portable thing for that, but eh. WG14 works slowly
<sham1> Problem with header guards is that they pollute the namespace
<sham1> Of course the real issue is that translation units are done in a silly way in C, but oh well, c'est la vie
<gog> #pragma once gang
<gog> but let's be honest, all programming is equally horrible
<mjg> #pragma not even once
<mjg> gog: it is not
<mjg> *equally* horrible
<kof123> "Problem with header guards is that they pollute the namespace " yes, or you can hash or something ugly :/
<kof123> #pragma not with a ten foot pole
* sakasama still writes old-fashioned header guards with the project name and mangled path concatenated.
<mjg> quite frankly i don't even see header guards
<sakasama> They're usually specially handled by compilers anyways.
<sham1> It's not even that they take space in a header, although that's also an issue
<sham1> It's that you have to come up with a globally unique preprocessor token to act as the guard thing
<sham1> But again, header guards and even #pragma once are just a symptom of headers and the way C achieves separate compilation
<gog> are we saying then, that C has deficiencies that have failed to be addressed over time?
<gog> perish the thought
<gog> it's a perfect programming language
<sham1> I know, a controversial claim
<sakasama> If your project doesn't have a globally unique macro prefix you're in trouble anyways.
<sham1> I'm piping hot with all these novel hot takes
<sham1> wombat: right. The thing is that you shouldn't need to
<sakasama> If there's a clash there, one of them needs replacement with sed and filenames typically end up being unique after mangling anyways, so in practice this isn't an issue for header guards any more than it is for macros and namespaces.
<zid`> C is *still* the least horrible language is the truely sickening thing about programming
<zid`> and it's got obvious 40 year old issues that are trivially fixed
<sakasama> Maybe if you have terrible paths like "vector/arc/tokens.h", "vector_arc/tokens.h", "vector/arc_tokens.h"...
<zid`> I've never, in all my life, included the same filename from different paths, into the same .c
<sakasama> I prefer my crippled version of C++.
<zid`> so imo FILE_H works fine as an include guard
<zid`> ime I should say
<sakasama> I'd prefix it with a project-specific token at least.
<zid`> mm probably
<zid`> but.. also nah
<zid`> if someone gets into trouble including my mem.h from boros into mem.h from my gamboy emulator into the same .c, they can fix it.
Jari-- has joined #osdev
<gog> fwiw only dorks like us use and argue about c
<gog> so it's fine if there's speedbumps
<zid`> my .h files are literally like 4 lines usually
<zid`> thing_new thing_destroy thing_do thing_do2
<zid`> decs for those
<sakasama> Adding the prefix not only avoids most of those conflicts, but also makes it easier to fix them when they occur since one can just sed that prefix in one of the projects.
<sakasama> It's worth the trivial effort, imho.
<zid`> I disagree
<zid`> I've written hundreds of headers and had to fix that problem 0 times, so not doing it is winning by a ratio of infinity to
<zid`> 1
<zid`> *or* we could fix the C processor language from 40 years ago to have #include default to 'once' and #again or something for repeated inclusion
<zid`> (for X-macros)
<zid`> (maybe not 'again', something that means 'once or once more idk', not just 'once more')
<zid`> maybe just make include how it is now, and add #once
<sakasama> I wonder if zig actually fixes C without massive frustrations.
<zid`> The real question
<zid`> is what do we name the fixed version of C I end up making
<zid`> C++ is taken, D is taken
<zid`> zig is taken
* sakasama still needs to evaluate zig.
<zid`> zid is too much like zig
<sakasama> I shall name it Narful.
<kof123> this could work for namespaces. zid_list. pkh_malloc there's only room for 26^3 coders, after that you have to wait for an opening. when someone dies you can get in.
<zid`> Narf is a good name
elastic_dog has quit [Ping timeout: 240 seconds]
<zid`> "What are we doing now binky?" "Trying to take over the world!" *Narf*
elastic_dog has joined #osdev
<sakasama> Pinky. Binky is something babies suck on.
<zid`> yea bypo
<zid`> tybo*
gog has quit [Quit: Konversation terminated!]
terminalpusher has joined #osdev
gog has joined #osdev
dutch has quit [Quit: WeeChat 3.8]
dutch has joined #osdev
pharonix71 has quit [Remote host closed the connection]
pharonix71 has joined #osdev
Jari-- has quit [Remote host closed the connection]
dude12312414 has quit [Remote host closed the connection]
dude12312414 has joined #osdev
joe9 has joined #osdev
bauen1 has quit [Ping timeout: 252 seconds]
linearcannon has quit [Remote host closed the connection]
<mjg> > It is traditional for the author to magnanimously accept the blame for whatever
<mjg> deficiencies remain. I don’t. Any errors, deficiencies, or problems in this book are
<mjg> somebody else’s fault, but I would appreciate knowing about them so as to deter-
<mjg> mine who is to blame.
<mjg> noice
<zid`> nice ligature nerd
terrorjack has quit [Ping timeout: 260 seconds]
terrorjack has joined #osdev
slidercrank has quit [Ping timeout: 252 seconds]
terrorjack has quit [Quit: The Lounge - https://thelounge.chat]
heat has quit [Remote host closed the connection]
heat has joined #osdev
terrorjack has joined #osdev
Terlisimo has quit [Quit: Connection reset by beer]
Terlisimo has joined #osdev
GeDaMo has quit [Quit: That's it, you people have stood in my way long enough! I'm going to clown college!]
Burgundy has quit [Remote host closed the connection]
ZombieChicken has joined #osdev
bradd has joined #osdev
ZombieChicken has quit [Remote host closed the connection]
danilogondolfo has quit [Remote host closed the connection]
ZombieChicken has joined #osdev
rnicholl1 has joined #osdev
Vercas6947 has joined #osdev
rnicholl1 has quit [Quit: My laptop has gone to sleep.]
Vercas694 has quit [Ping timeout: 255 seconds]
Vercas6947 is now known as Vercas694
rnicholl1 has joined #osdev
nyah has quit [Quit: leaving]
bauen1 has joined #osdev
<heat> is x2apic support worth it?
<gog> yes
<heat> thank you gog
<gog> yw
JudgeChicken has joined #osdev
ZombieChicken has quit [Ping timeout: 255 seconds]
rnicholl1 has quit [Quit: My laptop has gone to sleep.]
rnicholl1 has joined #osdev
x8dcc has joined #osdev
JudgeChicken is now known as ZombieChicken
foudfou has quit [Quit: Bye]
foudfou has joined #osdev
ZombieChicken has quit [Ping timeout: 255 seconds]
rnicholl1 has quit [Quit: My laptop has gone to sleep.]
wlemuel has quit [Quit: Ping timeout (120 seconds)]
wlemuel has joined #osdev
FreeFull has quit []