![](https://seccdn.libravatar.org/avatar/0a8a165c24ed29b3a196e9dab465794e.jpg?s=120&d=mm&r=g)
On Sunday, June 9, 2024 2:33:45 AM EDT you wrote:
Hi Loren,
On 6/9/24 2:25 AM, Loren Burkholder wrote:
Hey all!
I recently ordered a Milk-V Meles[0]; while it hasn't shipped yet, I'm hoping to port openSUSE to the board once I get it, so I thought I'd get a head start by figuring out what all is involved in porting openSUSE to a new RISC-V board. Can anybody give me any pointers to get started?
Thanks, Loren
actually, I was planning to do the exact same thing :)
Awesome! I'd love to collab with you on the port since you probably know more about the porting process than I do. I'm @lorendb:nheko.im on Matrix; feel free to ping me in https://matrix.to/#/#chat:opensuse.org to talk further about this. (As an aside, while there is a dedicated openSUSE ARM Matrix channel, there's nothing for RISC-V; I'll see if I can get an admin to set up a RISC-V channel.)
My Meles hasn't shipped either, but the first step would be to enable U-Boot by building a device tree + configuration. This should be quite easy since the TH1520 SoC is already upstreamed[0]. Milk-V have their own U-Boot fork, but it's important to try to have everything upstreamed, so build delta patches from their fork.
Lastly you'd have to build a JeOS package with a (potentially patched) kernel in OBS. You have to figure out which changes they have made to packages like kernel-firmware and apply those as patches.
Milk-V also has the config they use for their image here [1].
Thanks, this all looks useful. I'll poke around at it and see what I can learn. Loren
[0] https://source.denx.de/u-boot/u-boot/-/blob/master/arch/riscv/dts/th1520.dts... [1] https://github.com/milkv-meles/thead-kernel/blob/meles/arch/riscv/configs/re...
Best