From: Larry Finger <Larry.Finger@lwfinger.net>
To: tim.gardner@canonical.com
Cc: mb@bu3sch.de, stefano.brivio@polimi.it,
linux-wireless@vger.kernel.org,
Martin Pitt <martin.pitt@canonical.com>
Subject: Re: [PATCH] b43: Declare all possible firmware files.
Date: Thu, 07 Jan 2010 13:31:11 -0600 [thread overview]
Message-ID: <4B46367F.2020306@lwfinger.net> (raw)
In-Reply-To: <4B4633CE.30906@canonical.com>
On 01/07/2010 01:19 PM, Tim Gardner wrote:
> Larry Finger wrote:
>> On 01/07/2010 12:35 PM, Tim Gardner wrote:
>>> The following changes since commit 2c1f1895ef2aa8f0e5497893eff71304aef332e1:
>>> Linus Torvalds (1):
>>> Merge branch 'drm-linus' of git://git.kernel.org/.../airlied/drm-2.6
>>>
>>> are available in the git repository at:
>>>
>>> git://kernel.ubuntu.com/rtg/linux-2.6 b43
>>>
>>> Tim Gardner (1):
>>> b43: Declare all possible firmware files.
>>>
>>> drivers/net/wireless/b43/main.c | 34 ++++++++++++++++++++++++++++++++--
>>> 1 files changed, 32 insertions(+), 2 deletions(-)
>>>
>>> >From def1157eaeb397f0afab25b91db8bab3fcb8816c Mon Sep 17 00:00:00 2001
>>> From: Tim Gardner <tim.gardner@canonical.com>
>>> Date: Thu, 7 Jan 2010 11:10:38 -0700
>>> Subject: [PATCH] b43: Declare all possible firmware files.
>>>
>>> BugLink: http://bugs.launchpad.net/bugs/488636
>>>
>>> Enhances module information with the names of the firmware files
>>> that could be used by this driver. This helps tools like Jockey to
>>> correctly detect and/or install the firmware files relevant to
>>> this driver.
>>>
>>> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
>>> ---
>>
>> How does Jockey do the firmware installation? I'm not familiar with this tool.
>>
>> Larry
>>
>
> Jockey is the codename for the Ubuntu Hardware Manager tool developed
> and maintained by Martin Pitt. Its primary purpose is to assist with the
> installation of not-completely open source components. Examples include
> nVidia and Broadcom 'wl'. In this case, I believe jockey offers a choice
> of b43 or wl (if the PCI IDs overlap).
>
> Cc'ing Martin.
Assuming that Jockey does not violate Broadcom's copyright on these firmware
files, this approach is going to get a bit messy. There are two new kinds of
devices that are currently undergoing reverse engineering. Once code is
available for them, the number of firmware files will be increased by quite a
bit. My current /lib/firmware/b43 has 93 files in it. Having that many
MODULE_FIRMWARE macros seems wrong.
Larry
next prev parent reply other threads:[~2010-01-07 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 18:35 [PATCH] b43: Declare all possible firmware files Tim Gardner
2010-01-07 19:05 ` Larry Finger
2010-01-07 19:19 ` Tim Gardner
2010-01-07 19:31 ` Larry Finger [this message]
2010-01-07 19:43 ` Tim Gardner
2010-01-08 17:32 ` Martin Pitt
2010-01-08 19:05 ` Michael Buesch
2010-01-09 1:19 ` Tim Gardner
2010-01-09 3:47 ` Larry Finger
2010-01-12 10:08 ` Tim Gardner
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=4B46367F.2020306@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.pitt@canonical.com \
--cc=mb@bu3sch.de \
--cc=stefano.brivio@polimi.it \
--cc=tim.gardner@canonical.com \
/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;
as well as URLs for NNTP newsgroup(s).