I haven't had time to do set up power draw testing. You can put it in, but we may revisit this when those are done. If you have power consumption figures of your own, that'd help. -- Paul On Tue, Dec 6, 2011 at 12:04 PM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Thu, Nov 17, 2011 at 12:52:38AM +0100, Felix Fietkau wrote: >> On 2011-11-16 7:40 PM, Paul Stewart wrote: >> > In fact, could this be made contingent on whether there's an AP-mode >> > interface, since the problem you're encountering seems to only be in >> > AP mode? What troubles me, Felix, is your statement that " this >> > series fixes some "PCI error" crashes". Does this mean that you >> > haven't root-caused the problem, and that this may only partially mask >> > it? >> The existing code was wrong, especially for client mode. I only noticed >> that because I was investigating some AP mode crashes triggered by it. >> My main focus when fixing this stuff was actually client mode since >> that's the one most affected by this codepath. > > Are we satisfied w/ this series? Or does it still need work? > > John > -- > John W. Linville Someday the world will need a hero, and you > linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
