linux-kernel - Re: [PATCH] Fixup deb-pkg target to generate separate firmware deb.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080915133026.GB18246@earth.li>
Date:	Mon, 15 Sep 2008 14:30:26 +0100
From:	Jonathan McDowell <noodles@...th.li>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] Fixup deb-pkg target to generate separate firmware deb.

On Sat, Sep 13, 2008 at 06:28:53PM +0200, Frans Pop wrote:
> On Saturday 13 September 2008, Jonathan McDowell wrote:
> > Ta, I've fixed both the indents. I've also changed the firmware package
> > to be arch: all.
> 
> Although I agree that arch all is technically not incorrect, I wonder if 
> it is the smart thing to do it here.
> 
> The pkg-deb target is probably mostly, or even exclusively - used to build 
> custom kernels, and people might be crossbuilding kernels with different 
> configs and thus resulting in different firmware files from the same 
> source (thus same version) on the same system.
> I build amd64, i386 and armel that way on my main desktop system, all with 
> different configs (tuned mainly to keep the build time down).
> 
> Keeping the firmware package arch-specific would ensure that a firmware 
> package built with the config for one arch does not get overwritten by 
> one built for another arch with a different config.

There's nothing stopping you having several different configs for the
same arch that don't produce all the required firmware either. I think
the right answer if you're building lots of different kernels for
different machines in testing is probably to build a
linux-firmware-image that has everything in it, so that you don't have
to worry about upgrading it most of the time.

(Technically you could make the firmware image indicate which firmware
it provides, but I think that gets overly granular for not huge gain.)

J.

-- 
Web [                        Make friends.                         ]
site: http:// [                                          ]       Made by
www.earth.li/~noodles/  [                      ]         HuggieTag 0.0.23
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/