<bslsk05>
github.com: freebsd-src/lib/librt/sigev_thread.c at main · freebsd/freebsd-src · GitHub
<heat>
your venerable UNIX LEGACEY system creates a thread per SIGEV_THREAD event :^
<heat>
glibc suffers from the same fwiw
friedy has joined #osdev
q3lont has quit [Remote host closed the connection]
asecretcat has joined #osdev
heat has quit [Remote host closed the connection]
heat has joined #osdev
friedy has quit [Quit: Client closed]
andreas303 has quit [Server closed connection]
andreas303 has joined #osdev
Left_Turn has joined #osdev
kerravon has joined #osdev
FreeFull has joined #osdev
Turn_Left has joined #osdev
Left_Turn has quit [Ping timeout: 240 seconds]
xenos1984 has quit [Quit: Leaving.]
heat has quit [Remote host closed the connection]
heat has joined #osdev
sortie has quit [Ping timeout: 240 seconds]
eroux has quit [Remote host closed the connection]
sortie has joined #osdev
goliath has quit [Quit: SIGSEGV]
warlock has joined #osdev
xenos1984 has joined #osdev
PapaFrog has quit [Ping timeout: 252 seconds]
Left_Turn has joined #osdev
Turn_Left has quit [Ping timeout: 258 seconds]
slidercrank has quit [Ping timeout: 240 seconds]
sortie has quit [Ping timeout: 240 seconds]
goliath has joined #osdev
sortie has joined #osdev
dude12312414 has joined #osdev
k0valski18891 has joined #osdev
gmacd has joined #osdev
gmacd has quit [Ping timeout: 240 seconds]
xenos1984 has quit [Ping timeout: 240 seconds]
Vercas has quit [Quit: Ping timeout (120 seconds)]
Vercas has joined #osdev
xenos1984 has joined #osdev
eddof13 has joined #osdev
terminalpusher has quit [Ping timeout: 246 seconds]
kerravon has quit [Quit: Client closed]
terminalpusher has joined #osdev
xenos1984 has quit [Ping timeout: 240 seconds]
poggers has quit [Quit: Konversation terminated!]
xenos1984 has joined #osdev
gareppa has joined #osdev
danilogondolfo has quit [Remote host closed the connection]
gareppa has quit [Quit: Leaving]
heat has quit [Remote host closed the connection]
innegatives has joined #osdev
heat has joined #osdev
heat has quit [Remote host closed the connection]
heat has joined #osdev
gog has joined #osdev
meisaka has quit [Ping timeout: 240 seconds]
meisaka has joined #osdev
jjuran has quit [Server closed connection]
sinvet__ has joined #osdev
MaxLeiter9 has joined #osdev
AndrewYu has joined #osdev
ghostbuster has quit [Ping timeout: 240 seconds]
dutch has quit [Ping timeout: 240 seconds]
Andrew has quit [Ping timeout: 240 seconds]
ornx has quit [Ping timeout: 240 seconds]
sjs has quit [Ping timeout: 240 seconds]
sinvet has quit [Ping timeout: 240 seconds]
thaumavorio has quit [Ping timeout: 240 seconds]
MaxLeiter has quit [Ping timeout: 240 seconds]
j`ey has quit [Ping timeout: 240 seconds]
MaxLeiter9 is now known as MaxLeiter
thaumavorio has joined #osdev
ghostbuster has joined #osdev
sjs has joined #osdev
dutch has joined #osdev
j`ey has joined #osdev
ornx has joined #osdev
jjuran has joined #osdev
jjuran has quit [Remote host closed the connection]
jjuran has joined #osdev
dutch has quit [Client Quit]
<lechner>
Hi, UEFI uses a short machine type to differentiate the boot paths, such as grubx64.efi. Are those short codes defined anywhere, please? How about the corresponding long ones? Thanks! https://en.wikipedia.org/wiki/UEFI#Operating_systems
<puck>
it's defined where all the other uefi things are defined :p
heat has quit [Remote host closed the connection]
dutch has joined #osdev
heat has joined #osdev
terminalpusher has quit [Remote host closed the connection]
heat has quit [Remote host closed the connection]
<zid>
It's even linked
<zid>
directly from that page
heat has joined #osdev
<zid>
where short name of the machine type can be IA32, X64, IA64, ARM or AA64.[29]
<zid>
click the [29]
terminalpusher has joined #osdev
<zid>
it takes you to the uefi spec
<heat>
if something takes you to the uefi spec, DO NOT CLICK ON IT
<zid>
then there's table 3.4
<zid>
heat: agreed
<zid>
but some people are masochists
<puck>
the fun part is there's no official name for risc-v 64-bit boot file
<heat>
probably rv64?
<puck>
i think this probably stems from the fact the COFF spec for risc-v is .. kinda half-baked
<heat>
riscv64 in UEFI is very very new
<puck>
it only exists for relocating full binaries
<puck>
heat: i blame microsoft for this actually. they don't have a need to compile whatever the COFF .o equivalent is for rv64
<heat>
why microsoft?
<puck>
heat: guess who owns the COFF spec
<heat>
the half-bakedyness of riscv64 EFI has nothing to do with them
<puck>
yes it does
<puck>
> The PE Executable machine type is contained in the machine field of the COFF file header as defined in the Microsoft Portable Executable and Common Object File Format Specification, Revision 6.0
goliath has quit [Quit: SIGSEGV]
<heat>
vendors fucking send their shit upstream to the microsoft PE spec, they have nothing to do with this
<heat>
the same shit applies to loongarch
<heat>
i wouldn't be surprised if the loongarch PE spec was full of typos
<puck>
heat: it's three lines
<puck>
namely:
<puck>
relocations: IMAGE_REL_BASED_LOONGARCH32_MARK_LA (32-bit absolute address formed in two consecutive instructions)
<puck>
and IMAGE_REL_BASED_LOONGARCH64_MARK_LA (64-bit absolute address formed in *four* consecutive instructions)
<zid>
bootrsicv128.efi
<puck>
ah. four. because there's IMAGE_FILE_MACHINE_LOONGARCH32 and LOONGARCH64
<bslsk05>
learn.microsoft.com: PE Format - Win32 apps | Microsoft Learn
<heat>
that's funny
<heat>
PE is a funny format
<heat>
they all share almost all relocs
<puck>
heat: and the lerocations are image relocation only
<puck>
heat: the issue is the risc-v elf spec has relocations you can't represent in COFF
<zid>
here's my great idea
innegatives has quit [Quit: WeeChat 3.8]
<zid>
you provide a COFF that is just an ELF loader
<puck>
zid: the thing is, you can just objcopy once you have the ELF
<puck>
the actual reason i'm aware of this is someone trying to make the rust efi stuff compile to rv64, but it can't, because it can't link ELF .o files into a PE file, so you'd need to have an objcopy step :v
<heat>
yes obviously
<heat>
that's how the tianocore garbage build system does it too
<heat>
but they actually translate relocs
slidercrank has joined #osdev
<heat>
brb i'm busy actively fighting with efi atm
<puck>
heat: right, the dynamic relocations can all be represented
heat has quit [Remote host closed the connection]
<puck>
but the static ones were the issue when doing the compilation in all-COFF (i'm assuming you check the logs lol)
PapaFrog has joined #osdev
<lechner>
thanks, everone! i found table 3.4. risc-v 64 is in there, btw
<puck>
right. i was looking at an older spec
<gog>
i decided i'm going to reimplement unix
<gog>
just kidding, illumos is the only implementation of unix we need
<puck>
xv6!
<zid>
risc128 is there, I wtf'd at it
terminalpusher has quit [Remote host closed the connection]
<geist>
not entirely, it's mostly just reserved space for a possible extension, IIRC
<geist>
but it's a fairly straightforward logical extension
Nokurn has quit [Ping timeout: 258 seconds]
eddof13 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
eddof13 has joined #osdev
gmacd has joined #osdev
linear_cannon has joined #osdev
linearcannon has quit [Ping timeout: 252 seconds]
zxrom has quit [Ping timeout: 252 seconds]
zxrom has joined #osdev
gxt__ has quit [Remote host closed the connection]
gxt__ has joined #osdev
PapaFrog has quit [Quit: ZNC 1.8.2+deb2 - https://znc.in]
PapaFrog has joined #osdev
kerravon 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!]
slidercrank has quit [Ping timeout: 260 seconds]
qxz2 has joined #osdev
<Ermine>
Are GH actions free hours limited per-project or globally?
ThinkT510 has quit [Quit: WeeChat 3.8]
<mrvn>
risc128, tss. I just want vector opcodes in loops where the CPU determines the stride size, not the binary.
<mcrod>
hi
<mcrod>
i think a bee stung me in my ear.
ThinkT510 has joined #osdev
dutch has quit [Quit: WeeChat 3.8]
<moon-child>
variable length vectors are fraught
<zid>
mcrod: sure it isn't a spot/zit?
<morgan>
idk do your zits tend to loudly fly away afterwards
<zid>
he didn't say his ear flew off morgan smh, pay more attention
<morgan>
maybe thats what happened to van gogh
dutch has joined #osdev
<moon-child>
van gogh more like van go away amirite folks I'll be here all night
eddof13 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<morgan>
van go WHERE. van go road???
<mrvn>
road go bye bey
<mrvn>
moon-child: It's not variable length, just variable stride
<moon-child>
what do you mean by stride?
<mrvn>
the number of bytes the cpu does in one go
<moon-child>
how's that different from the vector size?
heat has joined #osdev
<heat>
So, erm, update from my phone. I tried to update my dbx manually from the firmware and it bricked itself, so now I can't disable secure boot nor boot shit, the only thing it can do is open the firmware settings
<heat>
TL;DR fuck me
heat has quit [Quit: Client closed]
<zid>
bios is better.
gmacd has quit [Ping timeout: 252 seconds]
<zid>
sick
<zid>
I rebooted, windows switched over to hyper-v cus I'd asked it to install WSL
<zid>
I need a tar ball to install linux to wsl, my VM no longer works because hyper-v is installed
<zid>
I hope I have gunzip for mingw somewhere..
heat has joined #osdev
<zid>
heat: bios is better
<heat>
Holy crap i cant find the SPI chip to save my life man
<heat>
I don't find a fucking CMOS battery either, just found the EC
<zid>
what's a dbx in this context
<heat>
Database of very bad not good sha256 hashes for UEFI apps
<heat>
Kept in flash
<zid>
oh, what device is this on then
<heat>
I loaded it from uefi.org, it ate it, now im fucked
<heat>
I fucked my laptop
<zid>
tell me what it is
<heat>
Figuratively, to be clear
<zid>
I will google things for you on a real monitor
<heat>
ASUS a542u
<heat>
I found a schematic that has EC and the SPI rom very nearby, but it doesn't seem to reflect realitt
<heat>
Reality
<heat>
It seems to share mobos with the x542u
<zid>
uq and uv also exist..
<zid>
and uqr..
<moon-child>
wait there's a blacklist? What's the point of that?
<heat>
Its the same garbage i think
<puck>
heat: hrm, what happnes if you try to disable secureboot?
<heat>
It hangs if it ever tries to look at dbx I think.... cant boot (hangs), cant go to the secure boot vars menu (hangs), can't reset with factory settings (hangs)
<heat>
moon-child: its so you can blacklist vulnerable hashes, like the semi recent windows bootloaders that all got blacklisted as they could be exploited to break secure boot
<zid>
and there's no ASUS EZFLASH hotkey or anything?
<heat>
Tried switching RAM spots (so hw change could mean wiping or some garbage), nothing
<zid>
hold power for 40 seconds?
<heat>
Tried that many times, didnt seem to work
<puck>
woooorst case you could flash a replacement bios with setup.efi replaced with like. efi shell
gmacd has joined #osdev
<heat>
I can't even find the SPI puck...
<puck>
no i mean via ezflash
<heat>
But it's signed
<puck>
is it?
<moon-child>
heat: oh vulnerable ok yeah that makes sense
<heat>
I fucking hope so
<zid>
can you get into ezflash? if you can't you might be able to trigger recovery mode regardless
<heat>
Yeah i can get into ezflash
<moon-child>
I was thinking for malicious stuff it would be easy to change bits
<puck>
heat: the PEI is, the boot sector is
<zid>
and reflashing to a random different minor version doesn't help?
<zid>
usually that triggers a cmos clear
<puck>
heat: but you can freely sideload your own efi binaries
<heat>
puck: every module Should Be
<heat>
(Tm)
<puck>
i found a boardview for the x542uq
<heat>
In theory there's no ring 0 code unsigned
<puck>
and i cannot find shit here but all i have is part numbers
<zid>
anyway, asus vivobook says to cmos reset, unplug power, hold power button for 40 seconds
<heat>
zid: interesting suggestion...
<zid>
I'd do the 40 second thing first, ezflash second, then cry third
<heat>
Let me try and reassemble this garbage again
<puck>
heat: the EC is the ITE chip, right?
<heat>
Yes puck
<heat>
Nothing looks large enough to be SPI eeprom, nothing looks like a traditional, large CMOS battery either
<zid>
large enough to be spi?
<zid>
mine are all 8 pin and microscopic
<puck>
heat: it's likely you have no CMOS battery
<zid>
like, 4mm per side
<heat>
Hmm
<puck>
heat: actually on the x542 board i'm looking at
<zid>
I've had laptops with real cmos batteries, so that you can remove the laptop battery and not lose your clock, before everything was nvram instead
<zid>
by which I mean, flash
<puck>
heat: to the .. side of the CPU whicih doesn't have the chipset
<puck>
heat: just above( or under, depending on your perspective) the ram slot
<puck>
or i've fgucked up and am looking at completely the wrong device
<puck>
which is totally possible
<heat>
Can you share wtf you're looking at?
<heat>
It's the same mobo btw
<zid>
why did you even take it apart?
gmacd has quit [Ping timeout: 240 seconds]
<heat>
Cuz i tried everything else but removing the cmos battery or some garbo