From: Greg KH <greg@kroah.com>
To: Joerg Albert <jal2@gmx.de>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"otus-devel@lists.madwifi-project.org"
<otus-devel@lists.madwifi-project.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [otus-devel] Release of Atheros 802.11n USB Linux driver
Date: Tue, 28 Oct 2008 08:18:22 -0700 [thread overview]
Message-ID: <20081028151822.GA8783@kroah.com> (raw)
In-Reply-To: <49071272.8050700@gmx.de>
On Tue, Oct 28, 2008 at 02:24:02PM +0100, Joerg Albert wrote:
> On 10/28/2008 12:35 AM, Luis R. Rodriguez wrote:
>
>> This is now fixed on the master branch, also the branch "for-upstream"
>> does a lot of cleanup I thought you may like before stuffing it into
>> staging like removing all KERNEL_VERSION checks, all wireless
>> extensions checks, some compile warnings, removal of compat, dos2unix,
>> use utf-8, etc. Unfortunately this still requires a specific version
>> of wpa_supplicant but it seems it works. Not sure what bars you have
>> for staging at this point.
>
> I was a bit disappointed to find binary-only firmware inside the driver
> (HalPlus/OTUS_FB50/{hpfwbu,hpfwuinit}.c which is downloaded into the device
> during startup (initially thought this to be a complete OpenSource driver
> :-(
Binary firmware for a device does make the driver still "open source"
except for how some people intrepret it.
It is legal from a kernel standpoint though, and so it is fine to add to
the kernel as-is.
> Unless the attitude towards binary chunks inside the Linux kernel have
> changed, I guess these should be moved into userspace using the
> firmware_class driver to access it.
Yes they should, patches gladly accepted :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Joerg Albert <jal2@gmx.de>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"otus-devel@lists.madwifi-project.org"
<otus-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [otus-devel] Release of Atheros 802.11n USB Linux driver
Date: Tue, 28 Oct 2008 08:18:22 -0700 [thread overview]
Message-ID: <20081028151822.GA8783@kroah.com> (raw)
In-Reply-To: <49071272.8050700@gmx.de>
On Tue, Oct 28, 2008 at 02:24:02PM +0100, Joerg Albert wrote:
> On 10/28/2008 12:35 AM, Luis R. Rodriguez wrote:
>
>> This is now fixed on the master branch, also the branch "for-upstream"
>> does a lot of cleanup I thought you may like before stuffing it into
>> staging like removing all KERNEL_VERSION checks, all wireless
>> extensions checks, some compile warnings, removal of compat, dos2unix,
>> use utf-8, etc. Unfortunately this still requires a specific version
>> of wpa_supplicant but it seems it works. Not sure what bars you have
>> for staging at this point.
>
> I was a bit disappointed to find binary-only firmware inside the driver
> (HalPlus/OTUS_FB50/{hpfwbu,hpfwuinit}.c which is downloaded into the device
> during startup (initially thought this to be a complete OpenSource driver
> :-(
Binary firmware for a device does make the driver still "open source"
except for how some people intrepret it.
It is legal from a kernel standpoint though, and so it is fine to add to
the kernel as-is.
> Unless the attitude towards binary chunks inside the Linux kernel have
> changed, I guess these should be moved into userspace using the
> firmware_class driver to access it.
Yes they should, patches gladly accepted :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-28 15:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 2:04 Release of Atheros 802.11n USB Linux driver Luis R. Rodriguez
2008-10-22 6:50 ` Greg KH
2008-10-23 6:26 ` Greg KH
2008-10-23 6:26 ` Greg KH
2008-10-23 11:11 ` Luis R. Rodriguez
2008-10-23 11:11 ` Luis R. Rodriguez
2008-10-27 23:35 ` [otus-devel] " Luis R. Rodriguez
2008-10-27 23:35 ` Luis R. Rodriguez
2008-10-28 0:29 ` Greg KH
2008-10-28 0:29 ` Greg KH
2008-10-28 0:55 ` Luis R. Rodriguez
2008-10-28 0:55 ` Luis R. Rodriguez
2008-10-28 5:56 ` Greg KH
2008-10-28 5:56 ` Greg KH
2008-10-28 14:17 ` Joerg Albert
2008-10-28 14:17 ` Joerg Albert
2008-10-28 5:54 ` Joey Krane
2008-10-28 5:54 ` Joey Krane
2008-10-28 13:24 ` Joerg Albert
2008-10-28 13:24 ` Joerg Albert
2008-10-28 15:18 ` Greg KH [this message]
2008-10-28 15:18 ` Greg KH
2008-10-22 8:28 ` Florian Fainelli
2008-10-22 8:28 ` Florian Fainelli
2008-10-22 16:13 ` Luis R. Rodriguez
2008-10-22 16:13 ` Luis R. Rodriguez
2008-10-22 10:05 ` Michael Renzmann
2008-10-23 23:37 ` Luis R. Rodriguez
2008-10-23 23:37 ` Luis R. Rodriguez
2008-10-24 6:28 ` [otus-devel] " Michael Renzmann
2008-10-24 6:28 ` Michael Renzmann
2008-10-24 13:41 ` Joerg Albert
2008-10-24 13:41 ` Joerg Albert
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=20081028151822.GA8783@kroah.com \
--to=greg@kroah.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=jal2@gmx.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=otus-devel@lists.madwifi-project.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.