From owner-freebsd-mips@FreeBSD.ORG Sat Dec 31 18:08:09 2011 Return-Path: Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBEF7106564A; Sat, 31 Dec 2011 18:08:09 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 670498FC12; Sat, 31 Dec 2011 18:08:06 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id pBVI6vqY081648 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 31 Dec 2011 11:06:58 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 31 Dec 2011 11:06:57 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20111231000638.d257448c.ray@ddteam.net> <98BA8EF5-E808-43F8-92A8-68B14CAF998F@lassitu.de> <2A05E0AA-5AA5-47FD-90EA-BD6B23A01EFE@lassitu.de> To: Adrian Chadd X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 31 Dec 2011 11:06:58 -0700 (MST) Cc: Aleksandr Rybalko , Stefan Bethke , freebsd-mips@FreeBSD.org Subject: Re: arge problem on MR3420 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2011 18:08:09 -0000 On Dec 31, 2011, at 9:06 AM, Adrian Chadd wrote: > On 31 December 2011 08:03, Stefan Bethke wrote: >=20 >>> How about adding a printf() to arge_start_locked() and arge_encap(), >>> see if they're constantly being called. >>=20 >> I'll do that next year :-) >=20 > :) take your time. >=20 >> I believe the BOOTP code starts before timers are running, would that = affect things? >=20 > DELAY and pause() should still be working though, iirc. I know because > DELAY() works fine during ath_hal probe/attach routines. Maybe using bootp in the boot loader will cause things to be setup = differently in the hardware that our current code doesn't expect? DELAY is fine, since it is a busy wait. pause/tsleep, however, are nops = before we start scheduling. Warner