From: "Pali Rohár" <pali.rohar@gmail.com>
To: Luciano Coelho <coelho@ti.com>, Felipe Balbi <balbi@ti.com>,
kev@ti.com, Shahar Levi <shahar_levi@ti.com>,
Kalle Valo <kvalo@codeaurora.org>, "Andrew F. Davis" <afd@ti.com>,
Guy Mishol <guym@ti.com>, Yaniv Machani <yanivma@ti.com>,
Arik Nemtsov <arik@wizery.com>, Gery Kahn <geryk@ti.com>,
Felipe Balbi <balbi@kernel.org>, Luciano Coelho <luca@coelho.fi>
Cc: David Woodhouse <dwmw2@infradead.org>,
Pavel Machek <pavel@ucw.cz>, Aaro Koskinen <aaro.koskinen@iki.fi>,
Ben Hutchings <ben@decadent.org.uk>,
David Gnedt <david.gnedt@platinumzone24.at>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin)
Date: Sun, 20 Mar 2016 00:40:25 +0100 [thread overview]
Message-ID: <201603200040.26045@pali> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 846 bytes --]
Hi!
In linux-firmware repository [1] is missing AP firmware for TI wl1251
chip. There is only STA firmware wl1251-fw.bin which supports managed
and ad-hoc modes.
For other TI wilink chips there are <CHIP>-ap.bin firmware files
(wl1271-fw-ap.bin and wl128x-fw-ap.bin) which support AP mode. But for
wl1251 firmware file with guessed name "wl1251-fw-ap.bin" is missing.
Do you have any idea what happened with AP firmware for ti wilink4
wl1251 wifi chip? Or where can be found? Guys from TI, can you help?
I see that STA firmware was added into linux-firmware tree in year 2013
by this pull request [2].
[1] - https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity
[2] - http://thread.gmane.org/gmane.linux.kernel/1566500/focus=1571382
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2016-03-19 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 23:40 Pali Rohár [this message]
2016-03-21 10:35 ` AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin) Kalle Valo
[not found] ` <878u1cglu3.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-03-21 11:01 ` Pali Rohár
2016-04-04 12:39 ` Pali Rohár
2016-04-06 11:30 ` Machani, Yaniv
2016-04-06 12:12 ` Pali Rohár
2016-04-06 12:30 ` Machani, Yaniv
[not found] ` <AE1C82FB3D0EC64DB1F752C81CBD1101390F685E-1tpBd5JUCm6IQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2016-04-06 19:07 ` Kalle Valo
[not found] ` <87lh4q4kuc.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org>
2016-04-06 19:12 ` Machani, Yaniv
2016-04-10 11:51 ` Pavel Machek
2016-04-11 11:41 ` Pali Rohár
2016-04-11 11:49 ` Machani, Yaniv
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=201603200040.26045@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=arik@wizery.com \
--cc=balbi@kernel.org \
--cc=balbi@ti.com \
--cc=ben@decadent.org.uk \
--cc=coelho@ti.com \
--cc=david.gnedt@platinumzone24.at \
--cc=dwmw2@infradead.org \
--cc=geryk@ti.com \
--cc=guym@ti.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kev@ti.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=shahar_levi@ti.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
--cc=yanivma@ti.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;
as well as URLs for NNTP newsgroup(s).