From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: David Sainty <david.sainty@dtsp.co.nz>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Vikram Kandukuri <Vikram.Kandukuri@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] DFU Driver and firmware for Atheros bluetooth chipset AR3011
Date: Tue, 17 Nov 2009 13:59:09 -0800 [thread overview]
Message-ID: <20091117215909.GE11382@tux> (raw)
In-Reply-To: <4B0319E1.5030000@dtsp.co.nz>
On Tue, Nov 17, 2009 at 01:47:13PM -0800, David Sainty wrote:
> Marcel Holtmann wrote:
> >> Also Vikram -- why not just ISC license the files as we do with ath9k ? Then also
> >> use:
> >>
> >> MODULE_LICENSE("Dual BSD/GPL");
> >>
> >> This would be more consistant with what we do with our other upstream Atheros
> >> modules.
> >>
> >
> > Since this is just a firmware loading driver, I prefer if you just keep
> > it GPL only. It is not worth going into too much details. Especially
> > since it looks inspired (nicely phrased) from bcm203x.c driver.
> >
>
> In the interests of supporting the device from *BSD operating systems
> it'd be nice if it was clear that the firmware itself could be included
> under a BSD licence.
Did you read the license? It allow free redistribution.
Luis
next prev parent reply other threads:[~2009-11-17 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 14:36 [PATCH] DFU Driver and firmware for Atheros bluetooth chipset AR3011 Kandukuri Vikram
2009-11-17 14:59 ` Marcel Holtmann
2009-11-17 17:45 ` Luis R. Rodriguez
2009-11-17 20:29 ` Marcel Holtmann
2009-11-17 19:11 ` Luis R. Rodriguez
2009-11-17 20:27 ` Marcel Holtmann
2009-11-17 21:47 ` David Sainty
2009-11-17 21:59 ` Luis R. Rodriguez [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-17 14:48 Vasanthakumar Thiagarajan
2009-11-17 14:48 Vikram Kandukuri
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=20091117215909.GE11382@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Vikram.Kandukuri@Atheros.com \
--cc=david.sainty@dtsp.co.nz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 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.