All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Gibson <hermes@gibson.dropbear.id.au>,
	jt@hpl.hp.com,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Orinoco Wireless driver bugs in 2.5.17
Date: Wed, 29 May 2002 10:42:22 -0700	[thread overview]
Message-ID: <20020529104221.I24843@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020522103834.B10921@bougret.hpl.hp.com> <E17Aams-0002Ue-00@the-village.bc.nu> <20020523012517.GM1001@zax> <1022697627.9255.272.camel@irongate.swansea.linux.org.uk>

On Wed, May 29, 2002 at 07:40:27PM +0100, Alan Cox wrote:
> On Thu, 2002-05-23 at 02:25, David Gibson wrote:
> > The signal/noise bit is probably a red herring.  We have problems with
> > the reporting of this, but it's mostly cosmetic.  I seem to have
> > confusing and contradictory information about how to interpret the
> > values the firmware reports.
> 
> Ok the old driver gets the noise level right, the newer one got it
> wrong, the current one gets it wrong. The good news is the old one
> works, the new one didnt, the current 2.4.19pre one does...
> 
> Alan

	David,

	In the linux-wlan-ng, I did implement a different algorithm to
report signal/noise in /proc/net/wireless, based on various info on
the list. Mark Matthews did check with some people and told me it was
the right algorithm for the Intersil firmware.
	Note that I'm not sure we ever got it right.
	Also, in the past, we had the min/max wrapper that avoided
"strange" values, and I think that's what people are mostly
complaining about. So, maybe we should reintroduce the min/max.
	Regards,

	Jean

  reply	other threads:[~2002-05-29 17:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 17:38 Orinoco Wireless driver bugs in 2.5.17 Jean Tourrilhes
2002-05-22 18:24 ` Alan Cox
2002-05-22 18:17   ` Jean Tourrilhes
2002-05-23  1:27     ` David Gibson
2002-05-23  1:25   ` David Gibson
2002-05-29 18:40     ` Alan Cox
2002-05-29 17:42       ` Jean Tourrilhes [this message]
2002-06-02 23:38       ` David Gibson
2002-06-03  1:08         ` Alan Cox
     [not found] <385229951@toto.iv>
2002-05-27  9:27 ` Peter Chubb
  -- strict thread matches above, loose matches on Subject: below --
2002-05-23  3:21 Erik McKee
2002-05-22  0:06 Peter Chubb
2002-05-22  1:53 ` David Gibson
2002-05-22 13:16   ` Alan Cox

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=20020529104221.I24843@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hermes@gibson.dropbear.id.au \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@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 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.