<rneese>
so has anyone been working on rustsbi for riscvboards
pedja has joined #riscv
<bjdooks>
not sure, i've not tried rust yet
jedix has quit [Ping timeout: 248 seconds]
<conchuod>
well, i suppose someone has if it exists since SBI is a risc-v thing?
<palmer>
I think we're using rustsbi, but we may have rewritten it already
Starfoxxes has quit [Ping timeout: 265 seconds]
jedix has joined #riscv
Starfoxxes has joined #riscv
jedix has quit [Ping timeout: 272 seconds]
jedix has joined #riscv
<drmpeg>
rneese: You can have multiple kernels with extlinux. Or am I missing something?
<rneese>
yes . i dont get what he was doing with grub. but yes you can have a boot menu
prabhakarlad has quit [Quit: Client closed]
<drmpeg>
ok.
<bjdooks>
uboot can parse extlinux, i'm fairly sure of it
<drmpeg>
Oh yeah, I use it all the time for stable testing.
<drmpeg>
On Unmatched, I build a .deb and it's all taken care of.
<another>
Have lots of kernels via u-boot-menu/extlinux
vagrantc has joined #riscv
statusfailed has joined #riscv
<statusfailed>
What's a good way to get started with bare metal programming for risc-v? Something I'd really like to understand better are the steps between "computer off" and "computer executing instructions" :'D
<palmer>
That’s board specific
<statusfailed>
Are there any boards that are very well documented / a bit more noob-friendly?
<statusfailed>
I'm looking at the HiFive1 but I don't really know enough to judge if it's a good choice
<statusfailed>
(I guess boards with an emulator would be nice too?)
<statusfailed>
I know QEMU has a 'virt' machine which can be used to run risc-v code, but I guess it would be nice to run on a real (or at least simulated real) machine
jacklsw has quit [Read error: Connection reset by peer]
Andre_H has joined #riscv
junaid_ has joined #riscv
cwebber has quit [Ping timeout: 260 seconds]
prabhakarlad has joined #riscv
aerkiaga has quit [Remote host closed the connection]
aerkiaga has joined #riscv
rburkholder has quit [Ping timeout: 268 seconds]
jedix has quit [Ping timeout: 264 seconds]
jedix has joined #riscv
epony has quit [Quit: QUIT]
<smaeul>
leah2: conchuod: problem with BL808 is that the MMU-less E907 core is really in charge, not the C906. So using most peripherals is going to require some firmware running on the E907 to do things like set up clocks and forward interrupts
<conchuod>
ohh that sounds like a lot of fun!
<smaeul>
the chip is designed to have Linux running in the "multimedia subsystem" sandbox
elastic_dog has quit [Ping timeout: 260 seconds]
elastic_dog has joined #riscv
rneese has quit []
prabhakarlad has quit [Quit: Client closed]
junaid_ has quit [Remote host closed the connection]
mictty has joined #riscv
<palmer>
smaeul: isn't that pretty standard for these sort of systems?
<palmer>
(or I guess, Arm-based systems in these markets)
BootLayer has quit [Quit: Leaving]
jedix has quit [Ping timeout: 268 seconds]
prabhakarlad has joined #riscv
jedix has joined #riscv
motherfsck has quit [Ping timeout: 248 seconds]
<leah2>
i dont mind flashing the e907 with whatever it needs to :p
theruran has quit [Quit: Connection closed for inactivity]
prabhakarlad has quit [Quit: Client closed]
jmdaemon has joined #riscv
tusko has quit [Remote host closed the connection]
motherfsck has joined #riscv
epony has joined #riscv
mictty has quit [Quit: leaving]
RustyStriker has joined #riscv
Andre_H has quit [Ping timeout: 272 seconds]
freakazoid332 has joined #riscv
frkzoid has quit [Ping timeout: 255 seconds]
RustyStriker has quit [Remote host closed the connection]
jay2718 has quit [Ping timeout: 246 seconds]
motherfsck has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
mthall has quit [Ping timeout: 252 seconds]
mthall has joined #riscv
tusko has joined #riscv
bauruine has quit [Remote host closed the connection]