linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: Larry Finger <larry.finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43legacy: Fix machine check errors for PPC architecture with BCM4306/2
Date: Sat, 15 Sep 2007 20:10:07 +0200	[thread overview]
Message-ID: <200709152010.07647.mb@bu3sch.de> (raw)
In-Reply-To: <46EC1F5A.7030800@lwfinger.net>

On Saturday 15 September 2007 20:07:22 Larry Finger wrote:
> Your comments may be correct; however, the fact remains that with a rev 4 BCM4306, the original code
> generates many, many machine checks on PPC architecture, and I get reads with all ones on i386
> indicating that the read is invalid. These all occur before the firmware is loaded. Making the
> "gmode" bit mimic the behavior of the phy_connected variable of bcm43xx gets rid of the problems on
> both platforms.

Sure. But if you workaround this like that, you could
as well get completely rid of the gmode bit, as you always force it on.
But I think that's not what we want. The real fix is simple. See below.

> The registers that error are not just the extended GPHY registers that caused 
> problems in the past, but all the PHY registers.

Nobody is talking about the extG registers.

> If you can suggest a reordering of the initialization that delays PHY setup until the "magic step"
> that eliminates this problem is done on/to the ssb backplane, I will be happy to test it. I was
> unable to find such a solution.

There is no reordering needed.
You just need to find out why phy->gmode was not set.
I think it's set based on the have_gphy and have_bphy bits.
So you need to look there why one of these is not set. That is the real
cause of the issue.

-- 
Greetings Michael.

  reply	other threads:[~2007-09-15 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 17:39 [PATCH] b43legacy: Fix machine check errors for PPC architecture with BCM4306/2 Larry Finger
2007-09-15 17:48 ` Michael Buesch
2007-09-15 18:07   ` Larry Finger
2007-09-15 18:10     ` Michael Buesch [this message]
2007-09-15 19:12       ` Larry Finger
2007-09-15 19:47         ` Michael Buesch
2007-09-15 21:01           ` Larry Finger
2007-09-15 21:58             ` Michael Buesch
2007-09-15 23:26               ` Larry Finger
2007-09-15 23:58                 ` Michael Buesch

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=200709152010.07647.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=larry.finger@lwfinger.net \
    --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 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).