All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux-firmware: Allow selection of bnx2x fw version
Date: Mon, 29 Feb 2016 13:51:47 +1100	[thread overview]
Message-ID: <874mcs9qkc.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACPK8XeYeRYPdw1rjpYKW=XyQuw+X7fAn3Ds-RJC+zifJUjsjA@mail.gmail.com>

Joel Stanley <joel@jms.id.au> writes:
> On Fri, Feb 26, 2016 at 7:09 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> I think adding new config to chose between different versions of a
>> given firmware is going a bit too far. If we were to do that for all
>> firmwares in linux-firmware, it would really increase the number of
>> Config.in options too much.
>
> Yeah, I do agree with this concern. It's unfortunate we don't have a
> variable we can test to see what the kernel version is.
>
>> Shall I suggest to install both versions of the firmware? The firmware
>> files are not that large, and if filesystem size is really a strong
>> issue, it is always possible to clean up the non-required firmware
>> files in a post-build script.
>
> In our case the extra ~640kB would be worth cleaning up. I like
> buildroot for the clean tiny images it produces; I think that's worth
> preserving.

Also, at some point we run out of room on flash.

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2016-02-29  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  4:31 [Buildroot] [PATCH] linux-firmware: Allow selection of bnx2x fw version Joel Stanley
2016-02-26  8:39 ` Thomas Petazzoni
2016-02-29  1:45   ` Joel Stanley
2016-02-29  2:51     ` Stewart Smith [this message]
2016-03-01  4:17       ` [Buildroot] [PATCH v2] linux-firmware: Update bnx2x firwmare version Joel Stanley
2016-03-01 21:17         ` Arnout Vandecappelle
2016-03-03  7:06           ` Joel Stanley

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=874mcs9qkc.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.