selve has quit [Remote host closed the connection]
selve has joined #riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #riscv
stephano has joined #riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #riscv
stephano is now known as stephano[away]
stephano[away] has quit [Quit: ZZZzzz…]
jmdaemon has quit [Ping timeout: 268 seconds]
jacklsw has joined #riscv
rneese_ has quit []
<sevan>
I was wondering, what was the thinking behind using EFI on risc-v, it's a fresh arch with no legacy technical debt, wouldn't a fresh approach be better or something not platform specific be better?
<sevan>
just curious, not trying to troll and start a fight. the idea of drive letters and drivers for uefi boggles my mind. (something dos-like was the best they could come up with when the engineers sat down to build the sucessor to bios?)
<sevan>
this is in the uefi shell if you have that payload
iooi has quit [Read error: Connection reset by peer]
iooi has joined #riscv
<pabs3>
being similar to other arches is a good idea, many arches switched to little-endian in recent times for eg
jmdaemon has joined #riscv
iooi has quit [Ping timeout: 248 seconds]
iooi has joined #riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #riscv
iooi has quit [Read error: Connection reset by peer]
<sevan>
pabs3: early boot firmware doesn't really matter to userspace. (either direction you're going to have to put effort into making something work and you ideally want to avoid shoehorning something which results in inheriting decisions that don't make any sense in your context.)
<sevan>
pabs3: power still supports best-endian mode ;) j/k
<pabs3>
power endianness is per-process even I heard
<sevan>
and same with cambridge limb
<pabs3>
limb?
<sevan>
arm
<pabs3>
heh
___nick___ has joined #riscv
<sevan>
didn't know that about power, which the hardware was more accessible.
___nick___ has joined #riscv
<pabs3>
RaptorCS is expensive but not IBM-expensive, so if you have disposable income it is doable
<pabs3>
anyway, UEFI. its a standard, people like standards
<pabs3>
personally I prefer the RaptorCS approach of libre firmware (almost) everywhere
<sevan>
openfirmware is an IEEE standard
<sevan>
:)
<sevan>
+1 re RaptorCS
<pabs3>
openfirmware is an unpopular standard compared to UEFI though?
<sevan>
it's generic and portable vs itanium firmware, backported to x86, ported to arm so windows can run easily :)