From: "Arend van Spriel" <arend@broadcom.com>
To: sedat.dilek@gmail.com
Cc: "Sedat Dilek" <sedat.dilek@googlemail.com>,
"Lennert Buytenhek" <buytenh@wantstofly.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lautriv <admin@coldplug.net>,
"Jim Cromie" <jim.cromie@gmail.com>,
"Ben Hutchings" <ben@decadent.org.uk>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Xose Vazquez Perez" <xose.vazquez@gmail.com>
Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361)
Date: Wed, 2 May 2012 09:59:30 +0200 [thread overview]
Message-ID: <4FA0E962.7040402@broadcom.com> (raw)
In-Reply-To: <CA+icZUV=qtXwVxb+uvQJcsza0y+6k2LHJFFPnECY0M=QWBexaQ@mail.gmail.com>
On 05/01/2012 03:54 PM, Sedat Dilek wrote:
> On Tue, May 1, 2012 at 2:51 PM, Lennert Buytenhek
> <buytenh@wantstofly.org> wrote:
>> On Sun, Apr 29, 2012 at 12:25:21AM +0200, Sedat Dilek wrote:
>>
>>>> On 1st sight, logs look fine:
>>>>
>>>> [21:52:52]<lautriv> [ 6.050967] ieee80211 phy0: 88w8361p v4,
>>>> 00173f3bdde3, STA firmware 2.1.4.25
>>>>
>>>> But WLAN connection is not that fast and stable as lautriv reports
>>>> (several abnormalities were observed).
>>>>
>>>> I requested a tarball which includes:
>>>> * dmesg (Linux-3.3.3)
>>>> * e_n_a (/etc/network/interfaces)
>>>> * ifconfig output
>>>> * iwconfig output
>>>> * iw_phy output
>>>> * ps_axu (WPA) output
>>>>
>>>> lautriv will be so kind to be around on #linux-wireless/Freenode the
>>>> next days (UTC+2: German/Swiss local-time).
>>>> Just ping him.
>>>>
>>>> Hope you have fun, together!
>>>>
>>>> - Sedat -
>>>
>>> A new tarball from lautriv with same outputs as before, but now tested
>>> with Linux-3.4-rc4.
>
> [ CC hauke (OpenWrt) and Ben Hutchings (linux-firmware maintainer) ]
>
>> The output looks good enough for me to ACK adding the PCI ID.
>>
>> Can the firmware being used here be submitted to the linux-firmware
>> git tree?
>
> I can't say much about the firmware [1] inclusion or the procedure of
> it into linux-firmware [2].
> Maybe, Ben can explain the procedure and what has to be considered
> before inclusion in linux-firmware.
> The original firmware and helper images were extracted from a Netgear
> Windows driver [1].
>
> From what I read in the OpenWrt forum posting [3]: You wanted to care
> for inclusion:
>
> "Firmware isn't included in the kernel tree anymore, there's the
> linux-firmware git tree for that these days. I will contact some
> people at Marvell to ask whether 8361P firmware can be included
> there."
Basically, all firmware in linux-firmware repository should be
accompanied with license information. Also you are signing off the patch
to add the firmware to the repository so you are bound to the
Developer's Certificate of Origin 1.1 in [1]. Having the firmware
extracted from a windows driver does not fall under that statement,
unless Marvell is ok with its redistribution. Recently a patch was
submitted for a README in the linux-firmware repository about the
process. It must be a binary patch. Easiest way is to use 'git
format-patch -B'.
Gr. AvS
[1] http://lxr.linux.no/linux+v3.3.4/Documentation/SubmittingPatches
[2] https://lkml.org/lkml/2012/4/21/177
next prev parent reply other threads:[~2012-05-02 8:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:08 [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361) Sedat Dilek
2012-04-27 9:14 ` Lennert Buytenhek
2012-04-27 9:22 ` Sedat Dilek
2012-04-27 9:40 ` Lennert Buytenhek
2012-04-27 9:42 ` Sedat Dilek
2012-04-27 9:46 ` Lennert Buytenhek
2012-04-27 9:56 ` Sedat Dilek
2012-04-27 9:58 ` Lennert Buytenhek
2012-04-27 10:12 ` Sedat Dilek
2012-04-27 10:17 ` Lennert Buytenhek
2012-04-27 10:57 ` Sedat Dilek
2012-04-27 13:29 ` Sedat Dilek
2012-04-27 18:58 ` Lennert Buytenhek
2012-04-27 21:53 ` Sedat Dilek
2012-04-28 22:25 ` Sedat Dilek
2012-05-01 12:51 ` Lennert Buytenhek
2012-05-01 13:54 ` Sedat Dilek
2012-05-01 15:49 ` Lennert Buytenhek
2012-05-02 1:12 ` Pat Erley
2012-05-02 2:38 ` Lennert Buytenhek
2012-05-02 8:58 ` Sedat Dilek
2012-05-02 7:59 ` Arend van Spriel [this message]
2012-05-02 13:53 ` Ben Hutchings
2012-05-07 16:09 ` Dan Williams
2012-05-07 16:42 ` Dan Williams
2012-05-07 18:26 ` Adrian Chadd
2012-05-11 8:01 ` Helmut Stengele
2012-05-01 12:47 ` Lennert Buytenhek
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=4FA0E962.7040402@broadcom.com \
--to=arend@broadcom.com \
--cc=admin@coldplug.net \
--cc=ben@decadent.org.uk \
--cc=buytenh@wantstofly.org \
--cc=hauke@hauke-m.de \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--cc=xose.vazquez@gmail.com \
/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