From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: iwlagn fails to assoc with nexus one in ad-hoc mode
Date: Wed, 09 Jun 2010 19:53:41 +0200 [thread overview]
Message-ID: <1276106021.14580.20.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100607.214612.26938385.davem@davemloft.net>
On Mon, 2010-06-07 at 21:46 -0700, David Miller wrote:
> When I try to associate
FWIW, it is not actually associating, the TIM error in the log means
that it's actually setting up an IBSS network (yeah we should silence
the error as it's expected ...). Just in case somebody got confused if
the nexus was actually acting as an AP, it's not.
johannes
prev parent reply other threads:[~2010-06-09 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 4:46 iwlagn fails to assoc with nexus one in ad-hoc mode David Miller
2010-06-09 16:58 ` reinette chatre
2010-06-09 17:33 ` David Miller
2010-06-09 19:10 ` reinette chatre
2010-06-09 19:12 ` David Miller
2010-06-09 19:17 ` reinette chatre
2010-06-10 1:20 ` David Miller
2010-06-09 17:53 ` Johannes Berg [this message]
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=1276106021.14580.20.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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