From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev <netdev@vger.kernel.org>,
rt2x00-devel@lfcorreia.dyndns.org,
Jean Tourrilhes <jt@hpl.hp.com>,
Florian.Rampp@web.de
Subject: Re: monitor_during_oper on rt*pci (or any other pcmcia card)?
Date: Thu, 1 Jun 2006 19:58:41 +0200 [thread overview]
Message-ID: <200606011958.45376.IvDoorn@gmail.com> (raw)
In-Reply-To: <1149162449.8877.72.camel@johannes>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Hi,
> Florian approached me with a project where you need a pcmcia card that
> can have monitor_during_oper. I'd use bcm43xx but unfortunately the
> signal strength calculations are way off right now, and that's another
> requirement.
>
> Can the rt family of cards be made to support this with reliable signal
> strength readings?
At this moment the rt2x00 drivers are not known for their correct signal
strength reporting. The reading is coming out of the registers but
it isn't working in all cases.
Even the legacy drivers from Ralink self are not known for their correct
behaviour but some issues around that have been traced to bugs in the
driver. But it could be possible the registers are wrong as well.
> Or maybe I should rephrase the questions: which pcmcia cards can support
> this in their hardware? I might be willing to port their drivers over to
> d80211 just to get some more familiarity with the stack...
>
> Now, if no one can point me to ones that do have working signal
> strength, I'll probably have to do more reverse engineering on bcm43xx
> to get some reliable readings :/
>
> Thanks,
> johannes
>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-01 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 11:47 monitor_during_oper on rt*pci (or any other pcmcia card)? Johannes Berg
2006-06-01 17:58 ` Ivo van Doorn [this message]
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=200606011958.45376.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=Florian.Rampp@web.de \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=netdev@vger.kernel.org \
--cc=rt2x00-devel@lfcorreia.dyndns.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;
as well as URLs for NNTP newsgroup(s).