lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CA+icZUV=qtXwVxb+uvQJcsza0y+6k2LHJFFPnECY0M=QWBexaQ@mail.gmail.com> Date: Tue, 1 May 2012 15:54:49 +0200 From: Sedat Dilek <sedat.dilek@...glemail.com> To: Lennert Buytenhek <buytenh@...tstofly.org> Cc: "John W. Linville" <linville@...driver.com>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, lautriv <admin@...dplug.net>, Jim Cromie <jim.cromie@...il.com>, Ben Hutchings <ben@...adent.org.uk>, Hauke Mehrtens <hauke@...ke-m.de> Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361) On Tue, May 1, 2012 at 2:51 PM, Lennert Buytenhek <buytenh@...tstofly.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." Some more concerns... Dunno, if [4] is really correct and how to use one and same device-id for 8363 ***and*** 8361P: ... { PCI_VDEVICE(MARVELL, 0x2a02), .driver_data = MWL8363, }, ... Curious about a statement from hauke... Adding the device-id in case of 8361P is not enough (see attached patch) I am looking forward to having support for 8361P soon. - Sedat - P.S.: I have re-added Readme and patch as there are new CCs. [1] ftp://downloads.netgear.com/files/wn311t_4_2_setup.exe [2] http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=summary [3] https://forum.openwrt.org/viewtopic.php?pid=110039#p110039 [4] https://dev.openwrt.org/changeset/21167 View attachment "mwl8k_extract_firmware_v2.txt" of type "text/plain" (1347 bytes) Download attachment "0001-mwl8k-Add-support-for-MWL8361P.patch" of type "application/octet-stream" (2171 bytes)
Powered by blists - more mailing lists