All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] d80211: Simplify channel & mode configuration
Date: Fri, 16 Feb 2007 12:01:10 -0500	[thread overview]
Message-ID: <1171645270.4153.2.camel@localhost.localdomain> (raw)
In-Reply-To: <200702151552.02331.flamingice@sourmilk.net>

On Thu, 2007-02-15 at 15:52 -0500, Michael Wu wrote:
> On Thursday 15 February 2007 15:15, Jiri Benc wrote:
> > > +	local->hw.conf.channel = chan->chan;
> > > +	local->hw.conf.channel_val = chan->val;
> > > +	local->hw.conf.power_level = chan->power_level;
> > > +	local->hw.conf.freq = chan->freq;
> > > +	local->hw.conf.phymode = mode->mode;
> > > +	local->hw.conf.antenna_max = chan->antenna_max;
> >
> > What about passing ieee80211_channel and ieee80211_hw_mode structures
> > instead of a ton of variables? (Just an idea, not a problem with the
> > patch.)
> >
> I was thinking that too, but I was trying to avoid driver api changes. I might 
> make a patch for it later if it still makes sense then.
> 
> > > +	if (local->curr_rates != mode->rates)
> > > +		rate_control_clear(local);
> > > +	local->curr_rates = mode->rates;
> > > +	local->num_curr_rates = mode->num_rates;
> > > +	ieee80211_prepare_rates(local);
> >
> > This will trigger rate control reinitialization when scanning on abg
> > cards. It's needed but not obvious at first sight. Perhaps some comment
> > would be useful here? (Again, not a problem with the patch, just
> > something I realized looking at the patch and thinking why the hell do
> > we do the reinitialization here?)
> >
> Yeah, this is why rate control never seems to work right on my system - 
> NetworkManager keeps scanning and resetting the rate control. I'm not sure 
> exactly how to fix it, so I just left it..

Hmm; NM shouldn't be resetting the rate explicitly.  If the driver
resets the rate on a scan, isn't that a problem in the driver?

Dan



  reply	other threads:[~2007-02-16 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10  4:25 [PATCH] d80211: Simplify channel & mode configuration Michael Wu
2007-02-10  4:43 ` Michael Wu
2007-02-15 20:15   ` Jiri Benc
2007-02-15 20:52     ` Michael Wu
2007-02-16 17:01       ` Dan Williams [this message]
2007-02-16 18:36         ` Michael Wu
2007-02-15 21:29   ` 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=1171645270.4153.2.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --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 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.