From: Felipe Contreras <felipe.contreras@gmail.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
Oleksij Rempel <linux@rempel-privat.de>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
linux-wireless Mailing List <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: I always need a miracle to connect with iwlwifi
Date: Sun, 10 Nov 2013 14:32:46 -0600 [thread overview]
Message-ID: <527fed6ec7a4c_1010cd9e844a@nysa.notmuch> (raw)
In-Reply-To: <527FC179.2040503@gmail.com>
Emmanuel Grumbach wrote:
> On 11/10/2013 06:26 PM, Felipe Contreras wrote:
> > That's better than not associating at all, ever.
>
> No because it would break the driver against all the working APs which
> are fortunately enough more common. Maybe you can rewrite mac80211 /
> iwlwifi to make things work differently so that PS would still work with
> good APs and association would work with yours. Fair enough. Go ahead.
Challenge accepted:
http://article.gmane.org/gmane.linux.network/290256
> > Wouldn't it make sense to timeout if there's no DTIM, and still
> > associate? It's better than not associating ever. Plus, if you already
> > know that power saving wouldn't work in this case, merely disable
> > powersave.
>
> I can't wait for your patch.
Good, because I already sent it.
With my patch if the AP sends the beacon correctly; power saving is enabled, if
not, association still works, but power saving is disabled.
How you could not imagine such patch is beyond me.
--
Felipe Contreras
next prev parent reply other threads:[~2013-11-10 20:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 6:24 I always need a miracle to connect with iwlwifi Felipe Contreras
2013-10-28 8:31 ` Oleksij Rempel
2013-10-28 9:23 ` Krishna Chaitanya
2013-10-28 9:37 ` Felipe Contreras
2013-10-28 11:00 ` Krishna Chaitanya
2013-10-28 15:54 ` Felipe Contreras
2013-10-28 9:38 ` Felipe Contreras
2013-10-28 9:52 ` Oleksij Rempel
2013-10-28 15:44 ` Felipe Contreras
2013-10-28 16:28 ` Oleksij Rempel
2013-10-28 17:12 ` Felipe Contreras
2013-10-28 18:00 ` Felipe Contreras
2013-10-28 18:28 ` Krishna Chaitanya
2013-10-28 18:43 ` Felipe Contreras
2013-10-28 19:27 ` Krishna Chaitanya
2013-10-28 20:06 ` Felipe Contreras
2013-10-28 20:44 ` Krishna Chaitanya
2013-10-28 21:32 ` Felipe Contreras
2013-10-29 14:23 ` Krishna Chaitanya
2013-11-02 5:46 ` Felipe Contreras
2013-11-02 16:57 ` Krishna Chaitanya
2013-11-02 17:06 ` Felipe Contreras
2013-11-02 19:13 ` Krishna Chaitanya
2013-11-02 20:05 ` Krishna Chaitanya
2013-11-08 8:35 ` Felipe Contreras
2013-11-08 13:14 ` Felipe Contreras
2013-11-08 14:06 ` Krishna Chaitanya
2013-11-08 14:18 ` Felipe Contreras
2013-11-08 20:30 ` Krishna Chaitanya
2013-11-08 20:52 ` Felipe Contreras
2013-11-09 13:10 ` Krishna Chaitanya
2013-11-09 16:52 ` Felipe Contreras
2013-11-09 19:10 ` Krishna Chaitanya
2013-11-09 21:24 ` Felipe Contreras
2013-11-09 21:37 ` Krishna Chaitanya
2013-11-10 6:31 ` Emmanuel Grumbach
2013-11-10 16:26 ` Felipe Contreras
2013-11-10 17:25 ` Emmanuel Grumbach
2013-11-10 20:32 ` Felipe Contreras [this message]
2013-10-28 20:37 ` Felipe Contreras
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=527fed6ec7a4c_1010cd9e844a@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=chaitanya.mgit@gmail.com \
--cc=egrumbach@gmail.com \
--cc=hostap@lists.shmoo.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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).