From: "Pali Rohár" <pali.rohar@gmail.com>
To: Pavel Machek <pavel@denx.de>
Cc: "Machani, Yaniv" <yanivma@ti.com>, "Chalmers, Kevin" <kev@ti.com>,
Kalle Valo <kvalo@codeaurora.org>, "Davis, Andrew" <afd@ti.com>,
"Mishol, Guy" <guym@ti.com>, Arik Nemtsov <arik@wizery.com>,
Gery Kahn <geryk@ti.com>, Felipe Balbi <balbi@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Ben Hutchings <ben@decadent.org.uk>,
David Gnedt <david.gnedt@davizone.at>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Tony Lindgren <tony@atomide.com>, "Menon, Nishanth" <nm@ti.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin)
Date: Mon, 11 Apr 2016 13:41:18 +0200 [thread overview]
Message-ID: <20160411114118.GT8413@pali> (raw)
In-Reply-To: <20160410115141.GD30188@xo-6d-61-c0.localdomain>
On Sunday 10 April 2016 13:51:41 Pavel Machek wrote:
> Is it "hardware can't do AP", "firmware can't do AP" or "current drivers
> do not support AP"?
We know that current linux TI wl1251.ko driver does not support AP. And
I'm still do not know if "hardware can do AP" or not. Also I'm not sure...
maybe current firmware can be "forced" for implementing AP mode.
David Gnedt implemented packet injection for wl1251.ko via JOIN firmware
command. And he wrote me that aircrack utils contains one application
which implementing full AP station in userspace just via packet
injection radiotap (which is supported by wl1251).
So maybe using other firmware (filter) commands together with current
packet injection implementation could be possible to create AP mode
(usable for standard hostapd daemon)? Just thinking...
Anyway, other TI wilink devices have different firmware for AP mode...
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2016-04-11 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 23:40 AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin) Pali Rohár
2016-03-21 10:35 ` 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 [this message]
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=20160411114118.GT8413@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=arik@wizery.com \
--cc=balbi@kernel.org \
--cc=ben@decadent.org.uk \
--cc=david.gnedt@davizone.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=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@denx.de \
--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).