linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kershaw <dragorn@kismetwireless.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Zhu Yi <yi.zhu@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: More 4965 woes
Date: Fri, 20 Jun 2008 09:15:44 -0400	[thread overview]
Message-ID: <20080620131544.GA31113@drd1813.lan> (raw)
In-Reply-To: <1ba2fa240806191253l2769dec3q2a49638eafe01e48@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

On Thu, Jun 19, 2008 at 10:53:22PM +0300, Tomas Winkler wrote:
> > On channel 36 things appear to work (well, as much as they do otherwise,
> > packet hanging still makes the device unusable).  I'm still confused as
> > to why the card can report it works on that channel, scan that channel,
> > see beacons, but then refuse to transmit.
> 
> There is a bug in the firmware. the fix is on the way. Unfortunately I
> cannot currently commit to
> to any particular day it will be published yet.

That's fair enough, good to hear.

> What AP do you use I don't see such bad behviour on A band.

Which do you mean - The failure of radar channels, or the severe
latency/packet loss?

The severe latency/packet loss happens any time I enable HT, if I'm
connected to a HT AP or not, 2.4ghz or 5ghz, in a clean RF environment.

-m

-- 
Mike Kershaw/Dragorn <dragorn@kismetwireless.net>
GPG Fingerprint: 3546 89DF 3C9D ED80 3381  A661 D7B2 8822 738B BDB1

"Remember the book store down the road?  That then became a book and coffee
shop?  Now it's a 24-hour just-coffee shop.  It's like evolution, only, without
the getting better."

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-06-20 13:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 13:24 More 4965 woes Mike Kershaw
2008-06-18  9:28 ` Zhu Yi
2008-06-18 15:41   ` Mike Kershaw
2008-06-19 13:41     ` Mike Kershaw
2008-06-19 19:53       ` Tomas Winkler
2008-06-20 13:15         ` Mike Kershaw [this message]
2008-06-20 14:24           ` Tomas Winkler

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=20080620131544.GA31113@drd1813.lan \
    --to=dragorn@kismetwireless.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.com \
    --cc=yi.zhu@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;
as well as URLs for NNTP newsgroup(s).