netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Arend van Spriel <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: [PATCH] bcma: don't fail for bad SPROM CRC
Date: Mon, 6 Feb 2012 14:48:57 +0100	[thread overview]
Message-ID: <20120206134857.GA3636@polaris.bitmath.org> (raw)
In-Reply-To: <4F2FD6D0.8070508@broadcom.com>

On Mon, Feb 06, 2012 at 02:34:08PM +0100, Arend van Spriel wrote:
> On 02/06/2012 02:26 PM, Henrik Rydberg wrote:
> > The brcmsmac driver is now checking the bcma SPROM CRCs, leaving some
> > chipsets unrecognized that were functional prior to the switch. In
> > particular, the current code bails out on recent Macbooks. This patch
> > simply ignores the outcome of the CRC check, with the argument that an
> > unrecognized SPROM should be treated similarly to a non-existing one.
> 
> Suggestion:
> 
> The brcmsmac driver is now registered as a bcma device driver. Some
> chipsets fail on SPROM CRC check in the bcma bus driver. This leaves the
> chipset unrecognized and the bcma bus is not registered so that brcmsmac
> is not probed. In particular, the current code .......

All fine with me. To avoid confusion, here is the patch again, with
the above inserted.

Thanks,
Henrik

---

From 57a4fbd1767b3c2e7c32d288b713e1b06e597bd6 Mon Sep 17 00:00:00 2001
From: Henrik Rydberg <rydberg@euromail.se>
Date: Tue, 31 Jan 2012 14:22:15 -0500
Subject: [PATCH] bcma: don't fail for bad SPROM CRC
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The brcmsmac driver is now registered as a bcma device driver. Some
chipsets fail on SPROM CRC check in the bcma bus driver. This leaves
the chipset unrecognized and the bcma bus is not registered so that
brcmsmac is not probed. In particular, the current code bails out on
recent Macbooks. This patch simply ignores the outcome of the CRC
check, with the argument that an unrecognized SPROM should be treated
similarly to a non-existing one.

Cc: Arend van Spriel <arend@broadcom.com>
Cc: Franky (Zhenhui) Lin <frankyl@broadcom.com>
Cc: Rafał Miłecki <zajec5@gmail.com>
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
 drivers/bcma/main.c |    4 +---
 1 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/drivers/bcma/main.c b/drivers/bcma/main.c
index febbc0a..ec31f7d 100644
--- a/drivers/bcma/main.c
+++ b/drivers/bcma/main.c
@@ -169,10 +169,8 @@ int bcma_bus_register(struct bcma_bus *bus)
 	err = bcma_sprom_get(bus);
 	if (err == -ENOENT) {
 		pr_err("No SPROM available\n");
-	} else if (err) {
+	} else if (err)
 		pr_err("Failed to get SPROM: %d\n", err);
-		return -ENOENT;
-	}
 
 	/* Register found cores */
 	bcma_register_cores(bus);
-- 
1.7.9

  reply	other threads:[~2012-02-06 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 13:26 [PATCH] bcma: don't fail for bad SPROM CRC Henrik Rydberg
2012-02-06 13:34 ` Arend van Spriel
2012-02-06 13:48   ` Henrik Rydberg [this message]
2012-02-06 17:08 ` Rafał Miłecki
2012-02-06 17:35   ` Henrik Rydberg
2012-02-06 19:28   ` Arend van Spriel

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=20120206134857.GA3636@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=arend@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=zajec5@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).