On Thu, 2 May 2019, Kevin Hilman wrote: > Paul Walmsley <paul.walmsley@xxxxxxxxxx> writes: > > > I'd recommend testing the DT patches with BBL and the open-source FSBL. > > That's the traditional way of booting RISC-V Linux systems. > > OK, but as you know, not the tradiaional way of booting most other linux > systems. ;) > > I'm working on getting RISC-V supported in kernelCI in a fully-automated > way, and I don't currently have the time to add add support for BBL+FSBL > to kernelCI automation tooling, so having u-boot support is the best way > to get support in kernelCI, IMO. That's great. Please keep hacking away on RISC-V support for kernelCI. My point is just that the U-boot and OpenSBI software stack you're working with is not going to be useful for automatic tests of some kernel patches yet. That stack is still very new, and was written around a non-upstream set of DT data. We are in the process of posting and merging patches to fix that, but it's going to take a few releases of both the kernel and those other boot stack components until things are sorted out in a more durable way. - Paul
