linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	"Broadcom Wireless" <bcm43xx-dev@lists.berlios.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/RFT] b43: LP-PHY: Implement channel switching for  rev2+/B2063 radio
Date: Thu, 13 Aug 2009 14:05:02 -0500	[thread overview]
Message-ID: <4A8463DE.7060402@lwfinger.net> (raw)
In-Reply-To: <200908132005.37769.mb@bu3sch.de>

Michael Buesch wrote:
> On Thursday 13 August 2009 20:00:47 Gábor Stefanik wrote:
>> (List re-CC-ed.)
>>
>> 2009/8/13 Michael Buesch <mb@bu3sch.de>:
>>> On Thursday 13 August 2009 19:50:16 Gábor Stefanik wrote:
>>>> 2009/8/13 Michael Buesch <mb@bu3sch.de>:
>>>>> On Thursday 13 August 2009 17:02:21 Gábor Stefanik wrote:
>>>>>> Rev.2+/B2063 will now hopefully show some signs of life, though
>>>>>> it won't work at full performance, as calibration is still missing.
>>>>>>
>>>>>> Signed-off-by: Gábor Stefanik <netrolller.3d@gmail.com>
>>>>>>  static void lpphy_baseband_rev0_1_init(struct b43_wldev *dev)
>>>>>> @@ -1369,7 +1370,7 @@ static int b43_lpphy_op_init(struct b43_wldev *dev)
>>>>>>       lpphy_baseband_init(dev);
>>>>>>       lpphy_radio_init(dev);
>>>>>>       lpphy_calibrate_rc(dev);
>>>>>> -     //TODO set channel
>>>>>> +     b43_switch_channel(dev, dev->wl->hw->conf.channel->hw_value);
>>>>> Does dev->wl->hw->conf.channel->hw_value already have a sane value here?
>>>> I think it should - hw->conf.channel was handed to us by mac80211.
>>>> http://bcm-v4.sipsolutions.net/802.11/PHY/LP/Init says "Set channel
>>>> with current chanspec as argument", and hw->conf.channel is our
>>>> equivalent of chanspec.
>>> hw->conf.channel was not handed to us at all. You simply pick it
>>> from mac80211's conf structure and _assume_ that it is initialized.
>>> In the other PHY implementations we use phyop_default_channel (or mandatory
>>> hardcoded channel values) in the PHY init only. I think you should do the
>>> same here. Mac80211 will make sure to select the correct channel later.
>> OK, I will use the default channel (though that's not exactly what the
>> spec says - Larry, is using the default channel correct?)
> 
> What on earth could be incorrect about it? It's an as arbitrary value as
> dev->wl->hw->conf.channel->hw_value would be.

I have not found anything that says what should be used. If the
channel is valid for the selected band, it should be as good as any.
> 
>>>>> Also please call b43_lpphy_op_switch_channel() instead of b43_switch_channel().
>>>> No, that would be wrong; the generic parts of b43_switch_channel also
>>>> need to be executed. See
>>> I don't see why. The generic parts are nothing that should be done at the PHY init.
>> Well, the spec says that the generic parts need to be run, so I
>> implemented it as such.
> 
> We do understand what the generic stuff does and it is not required at this point.
> 
>> Larry, is this part of the spec correct?
> 
> I'm pretty sure it is. But that does not mean we have to implement the same
> bullshit broadcom does ;)

Amen. I have to put it on the web site just in case it is important,
but it must be done that way _ONLY_ if found to be needed for
operation or performance.

Larry

      reply	other threads:[~2009-08-13 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 15:02 [RFC/RFT] b43: LP-PHY: Implement channel switching for rev2+/B2063 radio Gábor Stefanik
2009-08-13 15:45 ` Larry Finger
2009-08-13 17:40 ` Michael Buesch
     [not found]   ` <69e28c910908131050m94a0246s63b5aa57c7b25606@mail.gmail.com>
     [not found]     ` <200908131955.32283.mb@bu3sch.de>
2009-08-13 18:00       ` Gábor Stefanik
2009-08-13 18:05         ` Michael Buesch
2009-08-13 19:05           ` Larry Finger [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=4A8463DE.7060402@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=netrolller.3d@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 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).