Linux wireless drivers development
 help / color / mirror / Atom feed
From: Gopal Raman <graman@arubanetworks.com>
To: linux-wireless@vger.kernel.org
Subject: ath5k : Channel 149 thru 161 not working with compat-wireless-2.6.34.1
Date: Thu, 5 Aug 2010 00:15:36 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100805T020816-848@post.gmane.org> (raw)

Hi
I have an internal ath5k (0x17AB:0x8331) NIC and with the old madwifi style
drivers (ath_pci ver 0.9.4.5) channels 149 thru 161 work fine. I'm able to rx/tx
frames.

With compat-wireless-2.6.34.1 running on 2.6.27.48 kernel, I can't receive (nor
tx) on channels 149 thru 161. The driver sets the channel without any errors.
But can't rx any frames. When I force transmit on these channels nothing is seen
on the air. Channels 36 thru 60 work fine

Is this a known issue ?

Thanks
-gopal


             reply	other threads:[~2010-08-05  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05  0:15 Gopal Raman [this message]
2010-08-05  0:57 ` ath5k : Channel 149 thru 161 not working with compat-wireless-2.6.34.1 Gopal Raman
2010-08-05  2:20   ` Jonathan Guerin
2010-08-05 19:35     ` Gopal Raman
2010-08-10  1:59     ` Gopal Raman
2010-08-11 17:31       ` Bob Copeland

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=loom.20100805T020816-848@post.gmane.org \
    --to=graman@arubanetworks.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