From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 8 10:42:48 2009 Return-Path: Delivered-To: freebsd-mobile@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 608E0106566C; Tue, 8 Dec 2009 10:42:48 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id E860F8FC12; Tue, 8 Dec 2009 10:42:47 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id nB8Agkxu011975; Tue, 8 Dec 2009 11:42:46 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id nB8AgkcV014472; Tue, 8 Dec 2009 11:42:46 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id nB8Agk0E077549; Date: Tue, 8 Dec 2009 11:42:46 +0100 From: Andre Albsmeier To: Rui Paulo Message-ID: <20091208104246.GA18375@curry.mchp.siemens.de> References: <20091207163607.GA15625@curry.mchp.siemens.de> <9A2736AF-321C-4F39-9AE5-BD436F7C2808@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9A2736AF-321C-4F39-9AE5-BD436F7C2808@FreeBSD.org> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Andre Albsmeier , freebsd-mobile@FreeBSD.org Subject: Re: iwi: Possibly wrong interpretation of beacon->number in if_iwi.c? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2009 10:42:48 -0000 On Tue, 08-Dec-2009 at 01:05:21 +0000, Rui Paulo wrote: > On 7 Dec 2009, at 16:36, Andre Albsmeier wrote: > > What do people think? > > > This could be a new firmware interface. You might want to check out > how the latest Linux driver does this. They do it the same way (comparing the whole 32bit ints). I don't know about the firmware interface (no docs). Originally, FreeBSD-6 and FreeBSD-7 use the same fw (V3.0). 8+ uses V3.1. Our code in FreeBSD-6 is the same as in 7. I didn't have problems with 6 in the very same environment, however, I remember I had to raise bmissthreshold a bit which means that I actually had missed beacons (the whole code in question is only triggered on a beacon miss). I don't have any problems at home where I am only 2m away from the AP (possibly no missed beacons there). I have also seen other people report similarly insane numbers. I have also found reports on the net where the values were reasonable. As I said, I use fw V3.1 and not the original V3.0. I did so in FreeBSD-6 as well. To summarise things, here are my observations of how beacon->number behaves with different software: fw3.0 fw3.1 FreeBSD-6 OK OK FreeBSD-7 insane insane "insane" means that in 99% of all cases beacon->number is something like 0xabcdXYXY (abcd can be 0000). Maybe someone who got the docs can jump in here. -Andre