From: Kalle Valo <kvalo@codeaurora.org>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Lauri Kasanen <cand@gmx.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] carl9170: Clarify kconfig text
Date: Wed, 20 Apr 2016 10:59:44 +0300 [thread overview]
Message-ID: <87a8koiubz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <11418613.XH7h8m2RjK@debian64> (Christian Lamparter's message of "Mon, 18 Apr 2016 10:07:02 -0700 (PDT)")
Christian Lamparter <chunkeey@googlemail.com> writes:
> On Monday, April 18, 2016 07:42:05 PM Kalle Valo wrote:
>> Christian Lamparter <chunkeey@googlemail.com> writes:
>>
>> > On Monday, April 18, 2016 06:45:09 PM Kalle Valo wrote:
>> >
>> >> Why even mention anything about a "special firmware" as the firmware is
>> >> already available from linux-firmware.git?
>> >
>> > Yes and no. 1.9.6 is in linux-firmware.git. I've tried to add 1.9.9 too
>> > but that failed.
>> > <http://comments.gmane.org/gmane.linux.kernel.wireless.general/114639>
>>
>> Rick's comment makes sense to me, better just to provide the latest
>> version. No need to unnecessary confuse the users. And if someone really
>> wants to use an older version that she can retrieve it from the git
>> history.
>
> Part of the fun here is that firmware is GPLv2. The linux-firmware.git has
> to point to or add the firmware source to their tree. They have added every
> single source file to it.... instead of "packaging" it in a tar.bz2/gz/xz
> like you normally do for release sources.
>
> If you want to read more about it:
> <http://www.spinics.net/lists/linux-wireless/msg101868.html>
Yeah, that's more work. I get that. But I'm still not understanding
what's the actual problem which prevents us from updating carl9170
firmware in linux-firmware.
--
Kalle Valo
next prev parent reply other threads:[~2016-04-20 7:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 8:33 [PATCH] carl9170: Clarify kconfig text Lauri Kasanen
[not found] ` <1466768.7dLuLFSDol@debian64>
2016-04-16 14:18 ` [PATCH v2] " Lauri Kasanen
2016-04-16 15:32 ` Christian Lamparter
2016-04-18 15:45 ` Kalle Valo
2016-04-18 16:07 ` [PATCH v3] " Lauri Kasanen
2016-04-18 16:24 ` Christian Lamparter
2016-04-18 16:20 ` [PATCH v2] " Christian Lamparter
2016-04-18 16:42 ` Kalle Valo
2016-04-18 17:07 ` Christian Lamparter
2016-04-20 7:59 ` Kalle Valo [this message]
2016-04-20 21:11 ` [RESEND] Re: updating carl9170-1.fw in linux-firmware.git Christian Lamparter
2016-05-25 14:51 ` Ben Hutchings
2016-06-04 14:58 ` [v2] carl9170: Clarify kconfig text Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2016-04-18 16:47 [PATCH v2] " Xose Vazquez Perez
2016-04-18 17:10 ` Christian Lamparter
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=87a8koiubz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=cand@gmx.com \
--cc=chunkeey@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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