From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] New package: linux-firmware
Date: Thu, 26 Jan 2012 16:41:50 +0100 [thread overview]
Message-ID: <4F21743E.1000407@visionsystems.de> (raw)
In-Reply-To: <466d341f6889776d67143c3f5f55bf46@zacarias.com.ar>
Am 26.01.2012 16:33, schrieb Gustavo Zacarias:
> On 2012-01-26 12:23, Peter Korsgaard wrote:
>
>>>>>>> "Yegor" == Yegor Yefremov <yegor_sub1@visionsystems.de> writes:
>>
>> Yegor> Am 26.01.2012 16:13, schrieb yegorslists at googlemail.com:
>>
>> Yegor> So here we have another issue: how can I define if files should
>> Yegor> be copied to /lib/firmware or /lib/firmware/foo? ti-connectivity
>> Yegor> firmware files should go direct to /lib/firmware. This is not
>> Yegor> the case now.
>>
>> Ahh, I thought there would be a 1-to-1 relation between the
>> linux-firmware.git location an /lib/firmware. How do other distributions
>> handle it?
>
> At least for ti-connectivity it seems to be kept in /lib/firmware/ti-connectivity.
> Most of the time linux-firmware unpacks directly to /lib/firmware and that's it.
> Checking the kernel source...
>
> grep for "request_firmware" in the relevant drivers (for instance linux/drivers/net/wireless/wl12xx) and we get "ret = request_firmware(&fw, WL128X_FW_NAME"... grepping for FW_NAME gets us...
>
> wl12xx.h:#define WL1271_FW_NAME "ti-connectivity/wl1271-fw-2.bin"
> wl12xx.h:#define WL128X_FW_NAME "ti-connectivity/wl128x-fw.bin"
> wl12xx.h:#define WL127X_AP_FW_NAME "ti-connectivity/wl1271-fw-ap.bin"
> wl12xx.h:#define WL128X_AP_FW_NAME "ti-connectivity/wl128x-fw-ap.bin"
>
> So they are used in the directory no less...
You're right. This is a disadvantage of using the old kernel (2.6.37). Here WLAN driver searches for blobs directly without prepending a ti-connectivity. O.K. lets keep directory structure as is.
I replaced install with cp and have a problem, cause cp won't create a directory (ti-connectivity for example), but copies symlinks correctly. Any idea how to fix this?
Yegor
next prev parent reply other threads:[~2012-01-26 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:13 [Buildroot] [PATCH v4] New package: linux-firmware yegorslists at googlemail.com
2012-01-26 15:16 ` Yegor Yefremov
2012-01-26 15:23 ` Peter Korsgaard
2012-01-26 15:33 ` Gustavo Zacarias
2012-01-26 15:41 ` Yegor Yefremov [this message]
2012-01-26 16:13 ` Peter Korsgaard
2012-01-26 17:02 ` Thomas Petazzoni
2012-01-26 19:15 ` Peter Korsgaard
2012-01-26 18:58 ` Peter Korsgaard
2012-01-26 20:05 ` Yegor Yefremov
2012-01-26 20:49 ` Michael S. Zick
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=4F21743E.1000407@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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.