All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Martin Beran <info@berycz.net>
Cc: linux-wireless@vger.kernel.org, Piotr Haber <phaber@broadcom.com>
Subject: Re: bugreport Broadcom BCM4313
Date: Sat, 15 Dec 2012 17:36:13 -0600	[thread overview]
Message-ID: <50CD096D.1000504@lwfinger.net> (raw)
In-Reply-To: <50CCE126.6020503@berycz.net>

On 12/15/2012 02:44 PM, Martin Beran wrote:
> (sry for my mistake in the subject before, Broadcom BCM4313 it is)
>
> to clarify
> it is still asking for wpa key, but doesnt want to connect
>
> from irc:
>  > b6fc28a158076ca2764edc9a6d1e1402f56e1c0c is the bad commit
>  > it added usleep_range() instead of udelay()

Did you get a patch from IRC? If not, the one below will likely do the trick.

Larry



Index: wireless-testing-new/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_lcn.c
===================================================================
--- wireless-testing-new.orig/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_lcn.c
+++ wireless-testing-new/drivers/net/wireless/brcm80211/brcmsmac/phy/phy_lcn.c
@@ -1343,13 +1343,13 @@ static bool wlc_lcnphy_rx_iq_cal_gain(st

  	wlc_lcnphy_rx_gain_override_enable(pi, true);
  	wlc_lcnphy_start_tx_tone(pi, 2000, (40 >> 1), 0);
-	usleep_range(500, 500);
+	udelay(500);
  	write_radio_reg(pi, RADIO_2064_REG112, 0);
  	if (!wlc_lcnphy_rx_iq_est(pi, 1024, 32, &iq_est_l))
  		return false;

  	wlc_lcnphy_start_tx_tone(pi, 2000, 40, 0);
-	usleep_range(500, 500);
+	udelay(500);
  	write_radio_reg(pi, RADIO_2064_REG112, 0);
  	if (!wlc_lcnphy_rx_iq_est(pi, 1024, 32, &iq_est_h))
  		return false;

      reply	other threads:[~2012-12-15 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15 19:28 bugreport atheros ar8162 Martin Beran
2012-12-15 20:44 ` bugreport Broadcom BCM4313 Martin Beran
2012-12-15 23:36   ` 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=50CD096D.1000504@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=info@berycz.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phaber@broadcom.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 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.