From: Bob Copeland <me@bobcopeland.com>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: jon.fairbairn@cl.cam.ac.uk,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: AP: ath5k + hostapd occasionally sulks
Date: Thu, 10 Sep 2009 17:41:49 -0400 [thread overview]
Message-ID: <20090910214149.GA21037@hash.localnet> (raw)
In-Reply-To: <4AA94BAA.1070605@redfish-solutions.com>
On Thu, Sep 10, 2009 at 11:55:38AM -0700, Philip A. Prindeville wrote:
> FYI: The Windows 7 box associates and runs just fine with 9K driver
> with 2009-09-07. So it seems to be an issue with the 5K driver.
Okay, probably so. Multicast buffering may be broken again.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-09-10 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 17:53 AP: ath5k + hostapd occasionally sulks Philip Prindeville
2009-09-09 8:01 ` Jon Fairbairn
2009-09-09 13:00 ` Bob Copeland
2009-09-09 16:44 ` Philip Prindeville
2009-09-10 18:55 ` Philip A. Prindeville
2009-09-10 21:41 ` Bob Copeland [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-14 20:24 Marin Glibic
2009-09-04 8:05 Jon Fairbairn
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=20090910214149.GA21037@hash.localnet \
--to=me@bobcopeland.com \
--cc=jon.fairbairn@cl.cam.ac.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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).