linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: carl9170 firmware
Date: Tue, 17 Apr 2012 14:27:53 -0500	[thread overview]
Message-ID: <4F8DC439.103@lwfinger.net> (raw)
In-Reply-To: <201204172035.06023.chunkeey@googlemail.com>

On 04/17/2012 01:35 PM, Christian Lamparter wrote:
> On Tuesday, April 17, 2012 07:25:25 PM Larry Finger wrote:
>> Christian,
>>
>> A question regarding adding carl9170-1.fw to the openSUSE firmware package is
>> being discussed on the oS kernel mailing list; however, I do not see that one
>> in the linux-firmware git repo. Should it be there?
> Does the repo take source code releases? [much like the work we do for the
> kernel driver, or have you ever seen a binary release on this ML :D ]. The
> files on<http://wireless.kernel.org/en/users/Drivers/carl9170#Firmware_binary>
> are just for convenience.

AFAIK, the repo only takes binary files. With the source under GPL2, that should 
not be a problem; however, the fact that there are two versions with the same 
name would be trouble. Adding under that name has the possibility of breaking 
all the systems that use the other version.

Too bad that the newer firmware was not renamed carl9170-2.fw. Then both could 
be added to the repo and the driver could load whichever one it needed. 
Unfortunately, making that change now would be difficult to propagate back to 
all the stable versions, but you might consider it for V3.5 and forward. In 
conjunction with that change, submit the newer firmware to the firmware repo 
with the -2 name. That won't break anyone's system. Users for kernels up to 3.4 
will still see what they did before.

>> Is there a legal problem with redistribution?
> Not that I know of.

With a GPLv2 license, there will be no problem.

Larry


> Regards,
> 	Christian
>


  reply	other threads:[~2012-04-17 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 17:25 carl9170 firmware Larry Finger
2012-04-17 18:35 ` Christian Lamparter
2012-04-17 19:27   ` Larry Finger [this message]
2012-04-18 18:26     ` Christian Lamparter
2012-04-18 19:09       ` Larry Finger
     [not found] <CAEh_CyWdC+-mV+YhmoxS6dubWVN10utDim+GWmDLYCX9K9AkkQ@mail.gmail.com>
2011-09-14  9:50 ` Carl9170 Firmware Christian Lamparter
2011-09-14 13:09   ` J Igrap
2011-09-14 17:00     ` Christian Lamparter
2012-04-11 13:20       ` J Igrap
2012-04-11 16:54         ` Christian Lamparter
2012-04-11 17:24           ` J Igrap
  -- strict thread matches above, loose matches on Subject: below --
2011-09-13 21:21 Carl9170 firmware J Igrap

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=4F8DC439.103@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).