On Fri, Sep 30, 2022 at 6:37 PM Jim Fehlig wrote:
>
> On 9/29/22 23:43, Christian Ehrhardt wrote:
> > On Thu, Sep 29, 2022 at 11:30 PM Jim Fehlig wrote:
> >>
> >> On 9/28/22 06:45, christian.ehrha...@canonical.com wrote:
> >>> From: Christian Ehrhardt
> >>>
> >>> Riscv64 usually uses u-boot as
On 9/29/22 23:43, Christian Ehrhardt wrote:
On Thu, Sep 29, 2022 at 11:30 PM Jim Fehlig wrote:
On 9/28/22 06:45, christian.ehrha...@canonical.com wrote:
From: Christian Ehrhardt
Riscv64 usually uses u-boot as external -kernel and a loader from
the open implementation of RISC-V SBI. The
On Thu, Sep 29, 2022 at 11:30 PM Jim Fehlig wrote:
>
> On 9/28/22 06:45, christian.ehrha...@canonical.com wrote:
> > From: Christian Ehrhardt
> >
> > Riscv64 usually uses u-boot as external -kernel and a loader from
> > the open implementation of RISC-V SBI. The paths for those binaries
> > as
On 9/28/22 06:45, christian.ehrha...@canonical.com wrote:
From: Christian Ehrhardt
Riscv64 usually uses u-boot as external -kernel and a loader from
the open implementation of RISC-V SBI. The paths for those binaries
as packaged in Debian and Ubuntu are in paths which are usually
forbidden to
On 9/28/22 14:45, christian.ehrha...@canonical.com wrote:
> From: Christian Ehrhardt
>
> Riscv64 usually uses u-boot as external -kernel and a loader from
> the open implementation of RISC-V SBI. The paths for those binaries
> as packaged in Debian and Ubuntu are in paths which are usually
>
