On Saturday 15 September 2007 23:22:20 Larry Finger wrote:
> In b43legacy, the variable gmode is always set. With a BCM4306/2,
> and likely a BCM4301, a variable is needed to control the execution
> path through the PHY and radio initialization, otherwise there are
> attempts to read from invalid registers. On x86 platforms, these
> read failures cause no problems; however they lead to machine check
> errors for the ppc architecture. This patch reverts to the variable
> and semantics used in the V3 specifications. It has been tested on
> an i386 platform using special code to detect these invalid reads,
> and on at least one Powerbook.
>
> Signed-off-by: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
> Index: wireless-dev/drivers/net/wireless/b43legacy/b43legacy.h
> ===================================================================
> --- wireless-dev.orig/drivers/net/wireless/b43legacy/b43legacy.h
> +++ wireless-dev/drivers/net/wireless/b43legacy/b43legacy.h
> @@ -389,10 +389,10 @@ struct b43legacy_lopair {
> struct b43legacy_phy {
> /* Possible PHYMODEs on this PHY */
> u8 possible_phymodes;
> - /* GMODE bit enabled? */
> - bool gmode;
> + /* true if PHY registers can be accessed */
> + bool connected;
I am completely against re-adding the old broken "connected" semantics.
IMO, this is a step backwards. I was happy to finally get rid of
this, as it caused me a lot of headaches.
> /* Possible ieee80211 subsystem hwmodes for this PHY.
> - * Which mode is selected, depends on thr GMODE enabled bit */
> + * This will be either G or B mode */
> #define B43legacy_MAX_PHYHWMODES 2
> struct ieee80211_hw_mode hwmodes[B43legacy_MAX_PHYHWMODES];
Not sure why you change the comment here this way.
If you remove the "gmode" capability, you also limit
the number of hwmodes to one. So no array is needed here anymore.
But in the end, you are the maintainer, so you decide.
I personally would not re-add proven wrong stuff back to my driver.
--
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
