All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jiri Benc <jbenc@suse.cz>, John Linville <linville@tuxdriver.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] Add wireless statics to bcm43xx-d80211
Date: Wed, 23 Aug 2006 09:54:04 +0200	[thread overview]
Message-ID: <1156319644.3629.25.camel@ux156> (raw)
In-Reply-To: <44EB7403.10705@lwfinger.net>

On Tue, 2006-08-22 at 16:15 -0500, Larry Finger wrote:
> >> +	int maxssi;
> > 
> > Why is maxssi here? Can it really change between received frames?
> 
> No it cannot change between frames; however, the max value can be very different for different 
> drivers using d80211. On the bcm43xx, it is 60; whereas 100 seems to be a better value for the 
> rt2x00 chips. Adding it here seemed like a good way to handle this situation. Do you suggest 
> something else?

I think the question was intended to be: "why is it in
ieee80211_rx_status and not in struct ieee80211_hw?"

> Again to pass the differing values for different drivers.

Ditto here. Just stick it into struct ieee80211_hw instead.

> > I would suggest using -110 dBm as a floor (to be compatible with RCPI
> > definition, see mail from Simon Barber describing it). Or is there any
> > particular reason for -104 dBm?
> 
> It is the value previously used in the softmac version of bcm43xx. A value of -110 would obviously 
> be better.

Who maintains the softmac version now? :P
I'd suggest to just change it there too for consistency.

johannes

  reply	other threads:[~2006-08-23  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 13:29 [PATCH] Add wireless statics to bcm43xx-d80211 Larry Finger
2006-08-22 14:09 ` Jiri Benc
2006-08-22 21:15   ` Larry Finger
2006-08-23  7:54     ` Johannes Berg [this message]
2006-08-23 10:01     ` Jiri Benc

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=1156319644.3629.25.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=jbenc@suse.cz \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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.