From: Marcel Holtmann <marcel@holtmann.org>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: wireless-testing regression: iwl3945 scan fails
Date: Wed, 22 Jul 2009 18:24:31 +0200 [thread overview]
Message-ID: <1248279871.28545.126.camel@violet> (raw)
In-Reply-To: <1248278121.17896.2728.camel@rc-desk>
Hi Reinette,
> > > I just upgraded to rc3-wl (commit 225b6807) and my iwl3945 doesn't work
> > > anymore, even scan fails. I don't have time to investigate this right
> > > now, but I'll try to find some time during the evening.
> >
> > I have looked at this now a bit and I don't think this is an iwl3945
> > problem. Scanning seems to stall in some situations and iwl3945 doesn't
> > even receive the scan command.
>
> The patches we sent recently did undergo testing under various scenarios
> using wpa_supplicant. We have not done this testing after the
> 2.6.31-rc3-wl merge (yesterday) though. I just did a quick test on my
> 3945 using iwconfig to associate and it was able to do so on A and G
> bands. Looks like I need to do some wpa_supplicant testing.
can also at least get an IP address via DHCP and do some packet
transfer. I made the experience that DHCP works and then we get
disconnected seconds later.
Regards
Marcel
next prev parent reply other threads:[~2009-07-22 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 5:27 wireless-testing regression: iwl3945 scan fails Kalle Valo
2009-07-22 12:34 ` John W. Linville
2009-07-22 14:44 ` Kalle Valo
2009-07-22 15:55 ` reinette chatre
2009-07-22 16:24 ` Marcel Holtmann [this message]
2009-07-22 16:38 ` reinette chatre
2009-07-24 9:28 ` Kalle Valo
2009-07-25 5:55 ` Kalle Valo
2009-07-25 8:31 ` Johannes Berg
2009-07-25 9:18 ` Kalle Valo
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=1248279871.28545.126.camel@violet \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.