On Tue, Feb 23, 2010 at 3:15 PM, Pavel Roskin <proski@xxxxxxx> wrote: > The AR_IMR_S2 register sometimes cannot be read correctly. Instead of a > valid value, 0xdeadbeef is returned. The driver has been observed > writing that value back to AR_IMR_S2 after changing a few bits. > > Cache the register value in ah->imrs2_reg and always write chached value > to the register. > > Signed-off-by: Pavel Roskin <proski@xxxxxxx> What hardware was this seen with ? Can you enable PS debug to see if perhaps PS is left enabled when we try to configure hardware. When we touch some registers PS needs to be enabled, this could be a PS issue, unless of course you see this also when PS is disabled by default. Luis -- 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
