Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] New package: linux-firmware
Date: Thu, 26 Jan 2012 13:16:09 +0100	[thread overview]
Message-ID: <20120126131609.70b081f8@skate> (raw)
In-Reply-To: <ad47d31d76e74e891bacdf8b9470a643@zacarias.com.ar>

Le Thu, 26 Jan 2012 09:00:47 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :

> These constructs can get too long too fast, why not something like...
> 
> ifeq ($(BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT2XXX),y)
>      LINUX_FIRMWARE_FILES += rt2860.bin rt2870.bin rt30*.bin 
> LICENCE.ralink-firmware.txt
> endif
> 
> define LINUX_FIRMWARE_INSTALL_TARGET_CMDS
>      cp -af $(addprefix $(@D)/, $(LINUX_FIRMWARE_FILES)) 
> $(TARGET_DIR)/lib/firmware
> endef
> 
> Will be nicer when other people add their wanted firmware to the 
> package.

I was also going to propose something like this, so I fully agree with
Gustavo here.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-01-26 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 11:30 [Buildroot] [PATCH v3] New package: linux-firmware yegorslists at googlemail.com
2012-01-26 12:00 ` Gustavo Zacarias
2012-01-26 12:16   ` Thomas Petazzoni [this message]
2012-01-26 12:43   ` Peter Korsgaard
2012-01-26 12:47     ` Gustavo Zacarias
2012-01-26 12:57       ` Peter Korsgaard
2012-01-26 12:59         ` Gustavo Zacarias
2012-01-26 13:44       ` Yegor Yefremov
2012-01-26 13:53         ` Peter Korsgaard
2012-01-26 13:55         ` Gustavo Zacarias
2012-01-26 14:19           ` Yegor Yefremov
2012-01-26 14:45             ` Gustavo Zacarias

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=20120126131609.70b081f8@skate \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox