From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larry Finger Date: Thu, 18 Nov 2010 11:02:51 -0600 Subject: [PATCH] ssb: fail registration for unknown SPROM revision In-Reply-To: <1290098865.12596.6.camel@maggie> References: <1288823326-9686-1-git-send-email-zajec5@gmail.com> <1288823326-9686-2-git-send-email-zajec5@gmail.com> <20101116212321.GF10774@tuxdriver.com> <1290013976.2513.14.camel@maggie> <20101118162748.GB2468@tuxdriver.com> <1290098156.12596.2.camel@maggie> (sfid-20101118_174421_892253_3B53C8D3) <1290098865.12596.6.camel@maggie> Message-ID: <4CE55C3B.6020803@lwfinger.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= Cc: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , "John W. Linville" , linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org On 11/18/2010 10:47 AM, Michael B?sch wrote: > If it would really succeed to initialize the device, this would be a > regulatory issue, because the sprom contains various power amplifier > calibration data. I think it should rather fail and be fixed correctly > instead of incorrectly using rev1 in that case. I agree that it is better to fail than use incorrect power data. Would it be useful if the SPROM data were logged when the revision is crap? John: could you dump and post the data from yours? I would like to see how bad it is. Larry