From: Charles Gordon <digigordo@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Is there a bug in 2.6.29-rc8 support of Ad-Hoc mode?
Date: Tue, 25 May 2010 20:00:27 -0400 [thread overview]
Message-ID: <AANLkTin75H4DDeTvCRCDOrmif_He4b_TCC_dQzgdeVEz@mail.gmail.com> (raw)
I am trying to get a driver I'm developing to work with Ad-Hoc mode on
Linux 2.6.29-rc8. I am running into a problem. I have traced it down
to the routine ieee80211_scan_work. I use the following commands to
start Ad-Hoc mode:
ifconfig wlan0 down
iwconfig wlan0 mode Ad-Hoc essid "AdHocID"
ifconfig wlan0 up
What happens is that the iwconfig command starts a scan for other PCs
using the AdHocID before the second ifconfig command is executed
(while the interface is still down). When ieee80211_scan_work is
executed, it bails out at this statement:
/*
* Avoid re-scheduling when the sdata is going away.
*/
if (!netif_running(sdata->dev))
return;
This aborts the scan, but leaves local->sw_scanning set. This
prevents future scans from running. When ieee80211_start_scan
executes it bails out at this statement:
if (local->sw_scanning || local->hw_scanning) {
if (local->scan_sdata == scan_sdata)
return 0;
return -EBUSY;
}
Can someone either confirm that this is a known problem with
2.6.28-rc8, or tell me what my driver could be doing to cause this
problem?
Thanks for any help you can provide.
next reply other threads:[~2010-05-26 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 0:00 Charles Gordon [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 11:57 Is there a bug in 2.6.29-rc8 support of Ad-Hoc mode? Gordon, Charles
2010-05-26 13:28 ` John W. Linville
2010-05-26 15:07 ` Gordon, Charles
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=AANLkTin75H4DDeTvCRCDOrmif_He4b_TCC_dQzgdeVEz@mail.gmail.com \
--to=digigordo@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).