Re: regarding build speed on riscv64

On Tue, Sep 1, 2026 at 6:50 AM Adrian Bunk <[email protected]> wrote:

> On Mon, Aug 31, 2026 at 06:39:07PM -0400, Dominique Belhachemi wrote:
> > On Mon, Aug 31, 2026 at 4:55 PM Aurelien Jarno <[email protected]>
> wrote:
> >  ...
> >
> > In parallel, we continue to follow upstream kernel support for the K3,
> > > with the hope we can get everything in 7.4. Currently the PCI
> controller
> > > [2] and the thermal management chip [3] are missing, and a few smaller
> > > fixes that will likely go through the stable trees anyway. The bad news
> > > is that it 7.4 is currently scheduled for January [4], so 7.3 will be
> > > the LTS version that will go into Forky. This means we'll need to work
> > > with the kernel team to backport the corresponding patches into 7.3.
> > >
> > >
> > Would it be possible for Debian to procure and distribute 10 to 20 K3
> > boards to interested DDs?
>
> Money in Debian is a mess, and your suggestion is somewhere around € 10k.
>
> Why is it a mess? What happened?

> Having hardware available to individual maintainers for local testing and
> > debugging would certainly help unblock and strengthen the riscv64 port.
>
> What problems do you plan to debug where you need physical hardware?
>
> Boot issues, kernel panics, timeouts, extensions, GPU bringup, 3D
graphics, AI.

Like every release architecture (and many ports architectures) riscv64
> has a porterbox, which is usually what individual maintainers need for
> debugging issues.
>
> The porterbox has limited value to us:
isa : rv64imafdc_zicntr_zicsr_zifencei_zihpm_zca_zcd

Best
-Dominique