From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Re "linux-firmware: ship needed config txt files." commit Date: Fri, 29 Nov 2024 14:06:11 +0000 Message-ID: <425EC3E1-03ED-4093-8162-88C717838819@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6138261066731942264==" List-Id: --===============6138261066731942264== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, If I may chime in=E2=80=A6 Some hardware seems to load firmware and then a configuration file which has = some sort of settings. We didn=E2=80=99t ship those. To make things easier, we should simply ship everything. Disk space utilisati= on of /lib/firmware is already through the root and so some extra text files = probably won=E2=80=99t hurt. The script that checks for changes does not seem to filter out anything, so w= e don=E2=80=99t need any changes. -Michael > On 29 Nov 2024, at 11:50, Adolf Belka wrote: >=20 > Hi Arne, >=20 > That was me I am afraid. I remember seeing all the text files in the rootfi= le and thought that those are not firmware files and so would not be needed. >=20 > Obviously my assumption about those files not being needed was very wrong. >=20 > I will make sure not to do the same thing again. >=20 > It should be unlikely to happen again as @Michael has added the find-linux-= firmware-changes tool to the system now which should help make sure I don't r= emove needed files. >=20 > Apologies for my error. I hope it didn't cause you too many problems with t= he builds and testing before you discovered it. >=20 > Regards, >=20 > Adolf. >=20 --===============6138261066731942264==--