[itchyjunk] has quit [Read error: Connection reset by peer]
isaacwoods has quit [Quit: WeeChat 3.3]
eau has quit [Ping timeout: 260 seconds]
eau has joined #osdev
m3a has quit [Quit: leaving]
m3a has joined #osdev
m3a has quit [Client Quit]
m3a has joined #osdev
nickster1 has joined #osdev
nickster has quit [Ping timeout: 260 seconds]
nickster1 is now known as nickster
srjek has quit [Ping timeout: 268 seconds]
NieDzejkob has quit [Quit: No Ping reply in 180 seconds.]
adder` has joined #osdev
adder has quit [Ping timeout: 256 seconds]
ElectronApps has joined #osdev
<devcpu>
hey guys, i am trying to google the term "forward progress guarantee", but i get weird results, ot least i think they are weird since i don't know/understand what the term means, what does it mean?
<moon-child>
it's a property of a concurrent system, namely that it does not deadlock
ElectronApps has quit [Remote host closed the connection]
<devcpu>
moon-child: tyvm! could you please give an example? i can digest assembly, at least most of the times =)
<bslsk05>
web.archive.org: Expanded Main Page - OSDev Wiki
<chibill[m]>
I should get back into trying osdev for x86 type systems. Recently been focusing on my homebrew cpu at getting a basic bios and stuff written for it.
<GeDaMo>
How are you building your CPU? FPGA?
<chibill[m]>
Currently its just emulated in python until I can figure out some of the logic behind operations. (Like fetching instructions taking multiple cycles since they are 4 bytes each.) Going to build it in Digital which if I remember correctly will let me export to FPGA.
<chibill[m]>
Basically I am at the stage of figuring out how micro-coding works.
ElectronApps has quit [Remote host closed the connection]
sikki has quit [Ping timeout: 256 seconds]
heat has joined #osdev
<chibill[m]>
Welp time for the fun of building a cross compiler on the system for the first time in like 3 years xD. (Last had one for a class that used xv6 but that was on a whole different machine.)
<junon>
Or just use Clang.
<junon>
Clang is a cross compiler by default.
<heat>
it's a good idea to use multiple toolchains
<heat>
portability is nice
<junon>
Sure but clang is also a toolchain
<heat>
that is correct
<junon>
And GCC cross compilers aren't really different toolchains, just same one configured differently
<heat>
yes
<chibill[m]>
I am sort of surprised I have clang installed. Don't ever remember installing it.
<heat>
but llvm and gnu are two different toolchains and that's my point
<heat>
also /if you know what you're doing/(high entry barrier) you can skip the cross compiler if you're just compiling bare metal code for the host system
<heat>
userspace is a bit harder but also doable
sortie has joined #osdev
<chibill[m]>
Question is there a tutorial or guide to making make files? I never really understood them and I don't want to be typing huge long commands to compile my os
<zid>
rule: file_it_needs_first \n
<zid>
\t command to produce file called rule
<zid>
that's it
<chibill[m]>
By never understood I mean making my own from nothing. I can do pretty well modifying and expanding existing ones.
<zid>
a.exe: a.c\n\tgcc a.c -o a.exe
<heat>
generally you have your usual targets (install, clean, maybe run if you so desire), install for example should depend on your program's target and your program's target should depend on its object files, and the object files depend on their .c files (+ header dep files)
<heat>
ultimately you have a %.o: %.c \n\tgcc $< -o $@ $(CFLAGS) $(CPPFLAGS)
<bslsk05>
github.com: boros/Makefile at master · zid/boros · GitHub
<catern>
a memory model is a serialization mechanism, in both meanings of serialization
<catern>
this is a witticism that is extremely niche (the niche is 2 people, me and the other person I was just talking to about how shared memory is a technique for transferring large datastructures from one core to another core)
isaacwoods has joined #osdev
<catern>
(and obviously also a memory model is a serialization mechanism in the sense of providing sometimes-serial semantics to memory operations)
<eryjus>
zid: why did you choose not to have boot.bin dependent on linker.ld? (thinking of `$(filter-out *.ld,$^)` )
<zid>
eryjus: could have, wasn't important to my actual development cus I wasn't changing it
<zid>
(should have)
sprock has joined #osdev
dude12312414 has joined #osdev
dude12312414 has quit [Remote host closed the connection]
dude12312414 has joined #osdev
sortie has quit [Quit: Leaving]
sortie has joined #osdev
srjek has quit [Ping timeout: 268 seconds]
srjek has joined #osdev
<catern>
i hope people like my witticism
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
CaCode has joined #osdev
mahmutov_ has joined #osdev
sprock has quit [Ping timeout: 260 seconds]
srjek|home has joined #osdev
srjek has quit [Ping timeout: 264 seconds]
dennis95 has quit [Quit: Leaving]
dormito10 has joined #osdev
dormito has quit [Ping timeout: 268 seconds]
dormito has joined #osdev
dormito10 has quit [Ping timeout: 268 seconds]
dormito10 has joined #osdev
dormito has quit [Ping timeout: 268 seconds]
sprock has joined #osdev
dormito10 has quit [Ping timeout: 268 seconds]
dormito10 has joined #osdev
EtherNet has quit [Quit: vacations.]
Brnocrist has quit [Ping timeout: 268 seconds]
[itchyjunk] has quit [Read error: Connection reset by peer]
Brnocrist has joined #osdev
xenos1984 has quit [Quit: Leaving.]
<zid>
[14:21] <matja> ziddie
<zid>
[14:21] <matja> do you know if AMD publish microcode update changelogs?
<zid>
mxshift? :p
<mxshift>
I don't recall seeing them
<mxshift>
might be buried in AGESA dumps
<zid>
think we discussed that here like yesterday
mahmutov_ has quit [Read error: Connection reset by peer]
<zid>
<matja> microcode: microcode updated early to new patch_level=0x0a001143