From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "Nick Kossifidis" <mickflemm@gmail.com>
Cc: linville@tuxdriver.com, ath5k-devel@lists.ath5k.org,
linux-wireless@vger.kernel.org, jirislaby@gmail.com
Subject: Re: [PATCH] ath5k: discard 11g caps if reported by an ar5211 eeprom
Date: Mon, 12 Jan 2009 17:46:22 +0100 [thread overview]
Message-ID: <200901121746.23260.helmut.schaa@gmail.com> (raw)
In-Reply-To: <40f31dec0901120825i6ec6af4bq39e7e1be8459e846@mail.gmail.com>
Am Montag, 12. Januar 2009 schrieb Nick Kossifidis:
> 2009/1/12 Helmut Schaa <helmut.schaa@googlemail.com>:
> > At least one ar5211 card (GIGABYTE GN-WLMA101, 168c:0012 subsystem
> > 1458:e800) reports itself as 11g capable which seems to be a bug in the
> > eeprom. initvals.c assumes that ar5211 is only 11b capable and thus refuses
> > to initialize this card. Hence this patch changes the probing for 11g
> > capabilities to discard 11g capabilities for ar5211 cards which allows this
> > specific card to work fine in 11b and 11a modes.
> >
> > Signed-off-by: Helmut Schaa <helmut.schaa@googlemail.com>
> > ---
> >
> > Is anybody aware of 11g-capable ar5211 cards which would be limited by
> > this patch?
[...]
> This should be O.K. for now but i think AR5211 supports the so called
> "pureg" mode which means ofdm only g (no cck headers etc).
Sounds reasonable, yes.
> It seems
> radio (RF5111) supports g mode (it can be found on AR5212 abg cards)
I guess you mean RF2111, right? RF5111 should be 11a.
I've just found a product sheet at [1] that states that the RF2111
supports "802.11g draft standard". I guess that's exactly what you've
described as "pureg" mode.
Thanks,
Helmut
[1] ftp://ftp.riss-telecom.ru/pub/wireless/doc/atheros/AR5001X.pdf
next prev parent reply other threads:[~2009-01-12 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:04 [PATCH] ath5k: discard 11g caps if reported by an ar5211 eeprom Helmut Schaa
2009-01-12 16:25 ` Nick Kossifidis
2009-01-12 16:46 ` Helmut Schaa [this message]
2009-01-12 16:57 ` Nick Kossifidis
2009-01-12 18:35 ` Helmut Schaa
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=200901121746.23260.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mickflemm@gmail.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.