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
| ||
|
Date: Sun, 10 Apr 2016 13:51:41 +0200 From: Pavel Machek <pavel@...x.de> To: "Machani, Yaniv" <yanivma@...com> Cc: Pali Rohár <pali.rohar@...il.com>, Luciano Coelho <coelho@...com>, "Balbi, Felipe" <balbi@...com>, "Chalmers, Kevin" <kev@...com>, Shahar Levi <shahar_levi@...com>, Kalle Valo <kvalo@...eaurora.org>, "Davis, Andrew" <afd@...com>, "Mishol, Guy" <guym@...com>, Arik Nemtsov <arik@...ery.com>, Gery Kahn <geryk@...com>, Felipe Balbi <balbi@...nel.org>, Luciano Coelho <luca@...lho.fi>, David Woodhouse <dwmw2@...radead.org>, Aaro Koskinen <aaro.koskinen@....fi>, Ben Hutchings <ben@...adent.org.uk>, David Gnedt <david.gnedt@...tinumzone24.at>, Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>, Sebastian Reichel <sre@...nel.org>, Tony Lindgren <tony@...mide.com>, "Menon, Nishanth" <nm@...com>, "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin) Hi! > > > wl1251 does not support AP mode, so there is no firmware for it in > > > the tree. > > > > > > Regards, > > > Yaniv > > > > Hi Yaniv! I read on some TI whitepaper, that wl1251 hardware supports > > some Soft-AP mode. So I expect that either special FW is needed for it > > or somehow it is possible to use current released. Do you have any information about it? > > Hi Pali, > This must be some typo, the device does not support Soft-AP. > More than that, wl1251 family is not officially supported via the mainline Linux. > For Soft-AP, and other new features based on Linux you should use WiLink8 chip family. Too late for that, we already have the devices, and they were manufactured quite long time ago. Is it "hardware can't do AP", "firmware can't do AP" or "current drivers do not support AP"? Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists