freakazoid12345 has quit [Ping timeout: 250 seconds]
shicz2 has quit [Ping timeout: 245 seconds]
shicz2 has joined #riscv
Gravis has joined #riscv
aerkiaga has quit [Remote host closed the connection]
jacklsw has joined #riscv
<pierce>
i have a stupid question
<sorear>
no such thing
<pierce>
it may be linux specific, but with a rootfs.ext4 which gets flashed to this c910 board, there are 4 files in it, fw_jump.bin, ice_evb_c910.dtb, ramdisk.img and uImage. Where does the kernel live? in here or in the actual rootfs?
<pierce>
my gut feeling is that it's the uImage within this rootfs
<sorear>
plausible, but it really depends on what the earlier part of the boot chain looks like
<pierce>
i don't think i'm going to succeed anyway, as I have tried flashing the boot fs from the build artifacts which would have the fix that was described
<sorear>
if you're getting a desktop the kernel is booting quite fine, whatever it is
<pierce>
i got a feeling i bought an unsupported product and I shouldn't expect them to fix anything for it
<pierce>
yeah, the kernel is out of date apparently, and doesn't output a terminal over uart as expected
<sorear>
might be missing drivers, might be a wrong dtb (those *really* should be in ROM and not something you have to flash)
<pierce>
Yeah there's a lot of weird stuff going on. I flashed the android bootfs which has a different dtb filename which uboot doesn't point at, and it loads the proper LCD resolution
<pierce>
The problem is I'm not sure what's for the EVB board or the RVB board
<jrtc27>
uImage is the kernel yes
<jrtc27>
special u-boot file format
<jrtc27>
because why not
EchelonX has joined #riscv
<pierce>
So in that GitHub thread, apparently their buildroot branch doesn't support the RVB (which is what I have), so I don't even know if that kernel would actually run on it
<jrtc27>
I guess CONFIG_EFI=y is too hard for them
<pierce>
I can't seem to find sources for the kernel that boots debian which they have pre-built kernels for. But that has the bug
<pierce>
I'm just pretty stuck. There's no support. No one else has bought one afaik. And I'm teetering on the edge of my capabilities
<sorear>
I wouldn't put it past the board designers to have two or more kernels, some of which are not used, so all we can say for sure is "... is a kernel yes"
<sorear>
are the c910s actually that rare
<sorear>
?
<pierce>
sorear: Not rare, just expensive and limited with IO
<sorear>
always fun to guess what people here mean by "expensive"
<pierce>
AU $563.63 | T-head RVB-ICE Development Board,Dual-core XuanTie C910 RISC-V 64GC ,1.2GHz, Support Android/Debian System
<Sofia>
What is the closest to a developer workstation capable RISC-V based device? An unmatched with an attached GPU? Something faster?
<pierce>
It's out of order though and does have an embedded GPU which made it interesting to me
<pierce>
Unmatched is probably the best you're going to get today
<pierce>
Mine's collecting dust mainly due to the speed of it isn't great for compiling natively. And I'm too dumb to set up cross compilation in the setup I need/want
<Sofia>
My most powerful RISC-V core is qemu-riscv. :)
<pierce>
Yeah that's another thing I'm too dumb.to setup, but would love to see someone else do. Qemu running debian with 3d acceleration
<Sofia>
Or if that doesn't count a tiny E24 in a BL602 wifi module.
<Sofia>
pierce: I have a ~39.2MiB self-contained alpine chroot I can enter with `unshare -rR root /bin/sh`, with linux' binfmt configured to run all rv64 binaries under qemu-riscv64. No need to build a kernel. qemu-riscv64 glues the guest to the host.
<Sofia>
:)
<vagrantc>
my unmatched runs cooler than the risc-v cpu in my soldering iron