From: Jonathan McDowell <noodles@earth.li>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] Fixup deb-pkg target to generate separate firmware deb.
Date: Mon, 15 Sep 2008 14:30:26 +0100 [thread overview]
Message-ID: <20080915133026.GB18246@earth.li> (raw)
In-Reply-To: <200809131828.54286.elendil@planet.nl>
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
prev parent reply other threads:[~2008-09-15 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 11:20 Jonathan McDowell
2008-09-13 8:35 ` Frans Pop
2008-09-13 16:08 ` Jonathan McDowell
2008-09-13 16:28 ` Frans Pop
2008-09-15 13:30 ` Jonathan McDowell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080915133026.GB18246@earth.li \
--to=noodles@earth.li \
--cc=elendil@planet.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®