sorear changed the topic of #riscv to: RISC-V instruction set architecture | https://riscv.org | Logs: https://libera.irclog.whitequark.org/riscv
enoq has quit [Quit: enoq]
jay321_ has quit [Read error: Connection reset by peer]
jay321 has joined #riscv
paulk has quit [Ping timeout: 248 seconds]
paulk has joined #riscv
dlan_ is now known as dlan
Tenkawa has quit [Quit: Was I really ever here?]
MaxGanzII_ has joined #riscv
MaxGanzII_ has quit [Remote host closed the connection]
MaxGanzII_ has joined #riscv
sevan has quit [Changing host]
sevan has joined #riscv
meta-coder has joined #riscv
paulk has quit [Ping timeout: 240 seconds]
paulk has joined #riscv
jay321 has quit [Remote host closed the connection]
meta-coder has quit [Quit: leaving]
paulk has quit [Ping timeout: 248 seconds]
paulk has joined #riscv
jacklsw has joined #riscv
aerkiaga has quit [Remote host closed the connection]
billchenchina has joined #riscv
MaxGanzII_ has quit [Ping timeout: 240 seconds]
paulk has quit [Ping timeout: 268 seconds]
paulk has joined #riscv
andydude has joined #riscv
paulk has quit [Ping timeout: 265 seconds]
paulk has joined #riscv
heat has quit [Read error: Connection reset by peer]
heat_ has joined #riscv
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #riscv
jay321 has joined #riscv
jay321 has quit [Read error: Connection reset by peer]
jay321 has joined #riscv
paulk has quit [Ping timeout: 240 seconds]
paulk has joined #riscv
heat_ has quit [Remote host closed the connection]
heat_ has joined #riscv
andydude has quit [Quit: Leaving.]
frkazoid333 has quit [Read error: Connection reset by peer]
frkazoid333 has joined #riscv
heat_ has quit [Remote host closed the connection]
heat has joined #riscv
another| is now known as another
meta-coder has joined #riscv
BootLayer has joined #riscv
ashtin has joined #riscv
dev001 has joined #riscv
pecastro has joined #riscv
MaxGanzII_ has joined #riscv
Stat_headcrabed has joined #riscv
ldevulder has joined #riscv
Stat_headcrabed has quit [Quit: Stat_headcrabed]
danilogondolfo has joined #riscv
heat_ has joined #riscv
heat has quit [Read error: Connection reset by peer]
MaxGanzII_ has quit [Ping timeout: 240 seconds]
meta-coder has quit [Ping timeout: 268 seconds]
prabhakarlad has joined #riscv
enoq has joined #riscv
jay321 has quit [Remote host closed the connection]
meta-coder has joined #riscv
heat_ has quit [Remote host closed the connection]
heat_ has joined #riscv
jacklsw has quit [Quit: Back to the real world]
ncopa has joined #riscv
prabhakarlad has quit [Quit: Client closed]
MaxGanzII_ has joined #riscv
jn_ is now known as jn
aburgess has quit [Remote host closed the connection]
<ncopa> hi i got a visionFive 2 board. I tried to boot the debian image from the eMMC, but failed, so I tried an SD card. Also failed: https://tpaste.us/kXMZ
<ncopa> the goal is to boot alpine linux, but I wanted to make sure that it boots anything first
<ncopa> and have a look at the debian kernel config
<bjdooks> sounds like it either didn't find /boot/extlinux/extlinux.conf or there was an error in said file
<mps> ncopa: try different partitions with 'setenv mmcpart X' where X is partition number
<mps> default mmc part should be 'mmcpart=3', at least it is for VF V1
<ncopa> seems like I need to update the board firmware according this? https://jamesachambers.com/starfive-visionfive-2-firmware-update-guide/
<mps> but I don't see openSBI output on your log
aburgess has joined #riscv
<mps> not sure if it dislpays message on V2
<bjdooks> depends on config of uboot whether opensbi is verbose... i do wish howver they'd print the build version even if they don't splatter 200+ lines of output
<mps> someone here talked about booting V2. Tenkawa iirc
<mps> ah, ok, it shows
<ncopa> thats the obenSBI
<ncopa> OpenSBI v1.2
<mps> yes, and SBI version 1.0
<mps> sounds good
Andre_Z has joined #riscv
<mps> looks like incorrect mmcpart set in u-boot
<mps> but I'm not sure
<ncopa> should I try update the board firmware?
<mps> and I expected that V2 have newer u-boot by default
<mps> ncopa: idk. anyway my advice would be if you decide first make backup of original, just in case
<mps> according to fedex my board will arrive in about 10-15 days and then I will know more about booting it
<mps> now I'm just shooting in dark
prabhakarlad has joined #riscv
dev001 has quit [Ping timeout: 248 seconds]
meta-coder has quit [Quit: leaving]
heat_ is now known as heat
mahk has quit [Ping timeout: 240 seconds]
Tenkawa has joined #riscv
mahk has joined #riscv
dev001 has joined #riscv
mahk has quit [Ping timeout: 240 seconds]
mahk has joined #riscv
mahk has quit [Changing host]
mahk has joined #riscv
andydude has joined #riscv
dev001 has quit [Ping timeout: 240 seconds]
aerkiaga has joined #riscv
andydude has quit [Quit: Leaving.]
andydude has joined #riscv
crabbedhaloablut has quit [Ping timeout: 246 seconds]
crabbedhaloablut has joined #riscv
heat has quit [Read error: Connection reset by peer]
heat has joined #riscv
Stat_headcrabed has joined #riscv
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #riscv
andydude has quit [Quit: Leaving.]
heat_ has joined #riscv
heat has quit [Read error: Connection reset by peer]
Andre_Z has quit [Quit: Leaving.]
heat_ is now known as heat
vagrantc has joined #riscv
heat has quit [Read error: Connection reset by peer]
heat has joined #riscv
meta-coder has joined #riscv
andydude has joined #riscv
BootLayer has quit [Quit: Leaving]
dev001 has joined #riscv
<mps> bjdooks: just for info, we fixed booting alpine on visionfive V2
* mps is not bad shooter in the dark :)
<mps> if anyone want to try alpine on this board image is here https://dev.alpinelinux.org/~mps/riscv64/starfive-visionfive-mmc.img.xz
<mps> it is unified image for V1 and V2 with latest kernel made by Esmil
<mps> documentation will be updated later, hope on weekend
prabhakarlad has quit [Ping timeout: 245 seconds]
dev001 has quit [Remote host closed the connection]
<Tenkawa> mps: you tried aurel32's kernel yet? they are even newer
<mps> Tenkawa: first time hear for it
<mps> do you have url
<Tenkawa> yeah
<Tenkawa> just a sec
<Tenkawa> should be a jh7110-6.3.y.v2 branch in there
<mps> Tenkawa: thanks, will look over weekend if I can make it
<Tenkawa> np.. I'm running it on my vf2
<Tenkawa> Linux vf2 6.3.3-vf2+ #3 SMP Mon May 22 20:27:05 EDT 2023 riscv64 GNU/Linux
<Tenkawa> got a usb3 wifi on it and a nvme on it
meta-coder has quit [Quit: leaving]
ZipCPU has quit [Quit: ZNC 1.7.5+deb4 - https://znc.in]
<mps> does it work on vf1
<Tenkawa> still has some occasional iopoll hiccups with my parameters I added but its a lot better
<Tenkawa> so far not bad on my 1.2
jay321 has joined #riscv
<Tenkawa> that's only one I can speak for
<mps> I expect my vf2 board in two weeks, so I have time
<Tenkawa> hehehe
<Tenkawa> I am "trying" to adapt a Debian based build to my new Star64
ZipCPU has joined #riscv
<Tenkawa> only thing I've found are Yocto based so far
<Tenkawa> and I have no experience/desire to use it
rurtty has joined #riscv
<mps> for now I'm only interested to make alpine work as fine as possible
<Tenkawa> what does alpine use nowadays for package management?
<mps> 'apk' as always
<Tenkawa> Yeah I just haven't touched Alpine in eons
<andydude> I've always been impressed with alpine-linux
<andydude> aside from the whole musl/glibc incompatibilities, it usually "just works"
meta-coder has joined #riscv
<Tenkawa> yeah I've heard great things about musl when it doesn't have those glibc incompat's
BootLayer has joined #riscv
<mps> for normal use cases everything works on alpine. only some binary only things doesn't
andydude has quit [Quit: Leaving.]
bauruine has quit [Remote host closed the connection]
<Tenkawa> there's nothing "normal" about how I use machines
MaxGanzII_ has quit [Ping timeout: 240 seconds]
meta-coder has quit [Ping timeout: 240 seconds]
meta-coder has joined #riscv
rurtty has quit [Quit: Leaving]
aburgess has quit [Ping timeout: 246 seconds]
PobodysNerfect_ has quit [Quit: Gone to sleep. ZZZzzz…]
junaid_ has joined #riscv
Stat_headcrabed has quit [Quit: Stat_headcrabed]
PobodysNerfect has joined #riscv
andydude has joined #riscv
junaid_ has quit [Ping timeout: 240 seconds]
Trifton_ has joined #riscv
Trifton has quit [Ping timeout: 264 seconds]
PobodysNerfect has quit [Quit: Gone to sleep. ZZZzzz…]
PobodysNerfect has joined #riscv
PobodysNerfect has quit [Client Quit]
Trifton has joined #riscv
Trifton_ has quit [Read error: Connection reset by peer]
JanC has quit [Ping timeout: 264 seconds]
JanC has joined #riscv
MaxGanzII_ has joined #riscv
paulk-bis has joined #riscv
paulk has quit [Read error: Connection reset by peer]
aburgess has joined #riscv
Stat_headcrabed has joined #riscv
<drewfustini> Anyone know if ACLINT is ratified?
Stat_headcrabed has quit [Client Quit]
JanC has quit [Remote host closed the connection]
JanC has joined #riscv
sakman has joined #riscv
ashtin has quit [Quit: Leaving]
junaid_ has joined #riscv
prabhakarlad has joined #riscv
Trifton_ has joined #riscv
Trifton has quit [Ping timeout: 240 seconds]
pedja has joined #riscv
BootLayer has quit [Quit: Leaving]
ntwk has quit [Quit: ntwk]
ntwk has joined #riscv
fuwei has quit [Ping timeout: 240 seconds]
fuwei has joined #riscv
<palmer> drewfustini: the spec still says rc4, but that could mean anything
<drewfustini> thanks... I'll ask Anup
<drewfustini> AIA shows Q2'23 schedule for ratification though techinically ACLINT is separate
<palmer> the schedules are kind of worthless
<drewfustini> yeah, that is true
<drewfustini> Someone asked me if ACLINT is at the point to be incorporated into hardware designs and I couldn't figure out a proper answer
<palmer> if you've got some actual deliverable it's best to make sure you're not coupled to RVI schedules, it just makes a mess
<palmer> if the other option is just doing something custom, then probably best to go with the draft -- worst comes to worst it's different when ratified, but at least there's a chance it matches
<drewfustini> Yeah that makes sense
<palmer> definately trying to wait for RVI is a bad idea, just build the HW ;)
<drewfustini> Yeah, I'm a little worried it will be years before we see AIA hardware
<drewfustini> given that AIA is not even done yet
<palmer> I'm not worried, AIA is going to be chaos ;)
<drewfustini> :)
JanC_ has joined #riscv
<palmer> that's part of the reason it doesn't really matter if/when things are ratified, the specs are just too loosely written to have real compatibility before the HW shows up
JanC is now known as Guest3921
Guest3921 has quit [Killed (lead.libera.chat (Nickname regained by services))]
JanC_ is now known as JanC
<drewfustini> Yeah, I was reading through ACLINT and PLIC yaml files. It's interesting to see the variation
<drewfustini> I mean s/ACLINT/CLINT/
<drewfustini> it seems like SiFive was first so everyone else just used the SiFive documentation to for their PLIC and CLINT implementations... but with a few differences which in some cases made the drivers tricky
<palmer> ya, I think the CLINT and PLIC aren't really aimed at ratification -- it's sort of just a "start with SiFive's stuff and do whatever" type thing
<palmer> I doubt we're going to get better for a bit
<drewfustini> CLIC aka "fast interrupts" spec seems to be wallowing with discussion after discussion. At least it seems like Ventana cares about pushing AIA and ACLINT forward.
<drewfustini> I think it would probably be difficult for an existing SoC vendor dipping their toe into RISC-V to know what to do: just stick with the old de-facto CLINT and PLIC, or try to figure out the parts of ACLINT and AIA that are stable enough to implement
<palmer> ya, it's a mess
<palmer> but also it kind of doesn't matter, and SOC vendors don't tend to worry about this stuff anyway -- they're just going to go do whatever they want, regardless of what the specs say
<drewfustini> and just have to do the drivers themselves?
<palmer> ya, pretty much. Unless the product requires upstream kernel support they'll just release some forked old kernel
vagrantc has quit [Quit: leaving]
<palmer> it's pretty common, the BL folks have had to drag along old SOC vendor code a bunch so I'm sure they're got stories ;)
<drewfustini> Yeah... I suppose it is too difficult for a SoC vendor to guess right with a pre-ratified spec.
<palmer> or even post-ratified: between how vague the specs are and how much things change, it's not like ratification even matters for compatibility
<drewfustini> I think some traditionally ARM-based SoC vendors considering RISC-V get a bit afraid when they realize the specs are less concrete than what they might have been used to in the ARM world
<palmer> it's a double-edged sword: some of the vendors like having no rules, but the ones who have higher-quality software support targets tend to get scared off
<drewfustini> I am thinking especially for automotive and industrial focused vendors whose customers care a lot of about long term support
<drewfustini> s/for/about/
<palmer> ya, those guys should be terrified of RISC-V ;)
<drewfustini> :D
meta-coder has quit [Ping timeout: 264 seconds]
jay321 has quit [Remote host closed the connection]
Trifton_ has quit [Remote host closed the connection]
Trifton_ has joined #riscv
JanC has quit [Remote host closed the connection]
JanC has joined #riscv
ahs3 has quit [Ping timeout: 264 seconds]
ahs3 has joined #riscv
JanC has quit [Remote host closed the connection]
JanC has joined #riscv
junaid_ has quit [Remote host closed the connection]
ldevulder has quit [Quit: Leaving]
meta-coder has joined #riscv
<muurkha> palmer: hmm, shouldn't they be delighted at RISC-V? with ARM they're dependent on their chip suppliers being able to continue to get an ARM license, so they're dependent on both the chip vendor and on ARM
<muurkha> whereas with RISC-V they're only dependent on the chip vendor
<muurkha> and if the vendor has bolted something onto the side of the ARM core, like say a DSP accelerator, that's a risk factor that ARM might decide not to permit in the future
<muurkha> whereas with RISC-V the SoC vendors *can* do whatever they want regardless of what the specs say
meta-coder has quit [Quit: leaving]
<muurkha> is the alpine `apk` the same `apk` as on the Zaurus SL5500?
<mps> muurkha: no, apk is "Alpine Package Keeper"
<mps> it predate android apk and other similar named things
gordonDrogon has quit [Ping timeout: 264 seconds]
<mps> man apk, says "This apk has coffee making abilities." :)
gordonDrogon has joined #riscv
<muurkha> aha
<muurkha> thanks
lemoniter has joined #riscv
Tenkawa has quit [Quit: Was I really ever here?]
pedja has quit [Quit: Leaving]
JanC has quit [Remote host closed the connection]
JanC has joined #riscv
MaxGanzII_ has quit [Ping timeout: 240 seconds]
wingsorc has joined #riscv
danilogondolfo has quit [Quit: Leaving]
lemoniter has quit [Ping timeout: 264 seconds]
PobodysNerfect has joined #riscv
JanC has quit [Read error: Connection reset by peer]
JanC has joined #riscv
PobodysNerfect has quit [Quit: Gone to sleep. ZZZzzz…]
paulk-bis has quit [Ping timeout: 248 seconds]
paulk-bis has joined #riscv
enoq has quit [Quit: enoq]