Re: port-evbarm/58035: [RB] evbarm/earmv6: sshramdisk probably has firmware files in a wrong place

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

The following reply was made to PR port-evbarm/58035; it has been noted by GNATS.

From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Subject: Re: port-evbarm/58035: [RB] evbarm/earmv6: sshramdisk probably has firmware files in a wrong place
Date: Fri, 15 Mar 2024 18:15:29 +0000

 > Date: Fri, 15 Mar 2024 08:36:42 +0100
 > From: Martin Husemann <martin%duskware.de@localhost>
 >=20
 > Images in general are a separate step from release builds, but if this
 > image makes sense in that configuration it should be part of the arch
 > specific build.sh command run on the build cluster.
 >=20
 > If the portmaster (or whoever knows about the specifics) tells releng
 > this is trivial to adjust.
 
 This isn't a separate step.  The release build produces ramdisk.fs but
 not sshramdisk.fs because of the different recipes for the release
 target in their respective Makefiles:
 
 https://nxr.netbsd.org/xref/src/distrib/evbarm/instkernel/ramdisk/Makefile?=
 r=3D1.21#53
 https://nxr.netbsd.org/xref/src/distrib/evbarm/instkernel/sshramdisk/Makefi=
 le?r=3D1.26#57