Return-path: Received: from 80-190-117-144.ip-home.de ([80.190.117.144]:40838 "EHLO bu3sch.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968Ab1BNWBZ (ORCPT ); Mon, 14 Feb 2011 17:01:25 -0500 Subject: Re: Notes on ssb specs and implementation From: Michael =?ISO-8859-1?Q?B=FCsch?= To: =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= Cc: linux-wireless@vger.kernel.org, Larry Finger , b43-dev In-Reply-To: (sfid-20110214_205318_109392_FFFFFFFFAA87CB50) References: <1297282621.9734.5.camel@maggie> (sfid-20110214_205318_109392_FFFFFFFFAA87CB50) Content-Type: text/plain; charset="UTF-8" Date: Mon, 14 Feb 2011 23:01:17 +0100 Message-ID: <1297720877.5683.3.camel@maggie> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2011-02-14 at 20:51 +0100, Rafał Miłecki wrote: > W dniu 9 lutego 2011 21:17 użytkownik Michael Büsch napisał: > > On Wed, 2011-02-09 at 21:00 +0100, Rafał Miłecki wrote: > >> Michael: was there any reasons why we didn't implement some parts of > >> core-disabling code? > > > > The function are complete as of latest reverse engineering efforts. > > Broadcom added stuff, if they do more stuff in latest code. > > Nothing has changed in specs since 2006: > http://bcm-v4.sipsolutions.net/Backplane?action=info > For some reason routines that were present even in 2006 was not implemented. Well, so the function was implemented prior to 2006. Which doesn't surprise me. It was one of the first ones. > I've just written missing parts, May I see them? > tested and it still does not work :| > The only advantage discovered so far is that ssb detects sth is wrong > with IM state: > [ 2661.449647] ssb: Timeout waiting for bitmask 01800000 on register > 0F90 to clear. > > I can see wl experiencing the same problems after loading b43. It > reads 0xf90 dozen of times in a row. And that's the thing why I always avoid touching that function. There's so much magic going on, so that completely weird things happen all the time. :D -- Greetings Michael.