All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Luca Coelho <luca@coelho.fi>
Cc: <balbi@ti.com>, <ben@decadent.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<linux-wireless@vger.kernel.org>, Pavel Machek <pavel@denx.de>
Subject: Re: [PATCH] ti-connectivity: add wl1251 firmware and license
Date: Wed, 25 Sep 2013 08:59:43 -0500	[thread overview]
Message-ID: <20130925135943.GI10746@radagast> (raw)
In-Reply-To: <1380116535.4503.19.camel@porter.coelho.fi>

[-- Attachment #1: Type: text/plain, Size: 2605 bytes --]

On Wed, Sep 25, 2013 at 04:42:15PM +0300, Luca Coelho wrote:
> On Wed, 2013-09-25 at 08:23 -0500, Felipe Balbi wrote:
> > On Wed, Sep 25, 2013 at 02:07:58PM +0300, Luca Coelho wrote:
> > > On Wed, 2013-09-25 at 14:04 +0300, Luca Coelho wrote:
> > > > When sending big binary blobs, it's generally better to send pull
> > > > requests instead of patches.  If you add the -p option when calling git
> > > > pull-request, the text will include all the readable parts but will omit
> > > > the binary stuff.
> > > > 
> > > > Thank you very much for following up on this!
> > > 
> > > Ah, and I forgot to say that you should update the WHENCE file
> > > accordingly too.  Check the wl12xx and wl18xx drivers for examples.
> > 
> > I'll send a pull request, but how about this ? I don't think we can
> > change the license. It seems like the other firmwares are using the
> > older license, I'd argue those should be changed to the new one, but
> > that's another discussion.
> 
> Cool, in general it looks good!
> 
> Though it would be nice to know if the same "new" license could be used
> for all the firmwares to avoid almost identical licenses.

well, i'm not a lawyer :-s

> > diff --git a/WHENCE b/WHENCE
> > index e66fea5..4e9e2ed 100644
> > --- a/WHENCE
> > +++ b/WHENCE
> > @@ -1705,6 +1705,19 @@ Licence: Redistributable. See LICENCE.tda7706-firmware.txt for details.
> >  
> >  --------------------------------------------------------------------------
> >  
> > +Driver: wl1251 - Texas Instruments 802.11 WLAN driver for WiLink4 chips
> > +
> > +File: ti-connectivity/wl1251-fw.bin
> > +File: ti-connectivity/wl1251-nvs.bin
> 
> Don't you have the firmware version number to add here with "Version:"
> tags like the other ones? I think you can easily find the version by
> running strings on the binary and grepping for "Rev" (at least with the
> newer WiLinks, this works).

Done :-) thanks for the tip.

> > +Licence: See LICENCE.wl1251 for details.
> > +
> > +The driver expects to find the firmwares under a ti-connectivity subdirectory.
> > +So if your system looks for firmwares in /lib/firmware, the firmwares for
> > +wl12xx chips must be located in /lib/firmware/ti-connectivity/.
> 
> It's a bit stupid that this was never changed in wl1251, but it still
> expects the driver in the "root" firmwares directory (ie.
> in /lib/firmware/wl1251-fw.bin, not
> in /lib/firmware/ti-connectivity/wl1251-fw.bin).  Maybe now is the right
> time to change the driver appropriately to keep consistency? ;)

alright, will do...

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-09-25 14:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 14:44 [PATCH] ti-connectivity: add wl1251 firmware and license Felipe Balbi
2013-09-25 11:04 ` Luca Coelho
2013-09-25 11:07   ` Luca Coelho
2013-09-25 13:23     ` Felipe Balbi
2013-09-25 13:42       ` Luca Coelho
2013-09-25 13:59         ` Felipe Balbi [this message]
2013-10-02 12:55           ` [GIT PULL] firmware: wl1251 firmware binary Felipe Balbi
2013-10-04  5:01             ` Luca Coelho
2013-10-04 15:32               ` Felipe Balbi
2013-10-04 19:43                 ` Luca Coelho
2013-10-13 20:12             ` Ben Hutchings
2013-09-30  3:37       ` [PATCH] ti-connectivity: add wl1251 firmware and license Ben Hutchings
2013-09-30 13:32         ` Felipe Balbi
2013-09-25 12:54   ` Felipe Balbi

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=20130925135943.GI10746@radagast \
    --to=balbi@ti.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=pavel@denx.de \
    /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.