From owner-freebsd-arm@FreeBSD.ORG Wed Oct 15 16:25:38 2008 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14D291065694 for ; Wed, 15 Oct 2008 16:25:38 +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 C66CA8FC1E for ; Wed, 15 Oct 2008 16:25:37 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m9FGOE0N091115; Wed, 15 Oct 2008 10:24:14 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 15 Oct 2008 10:25:14 -0600 (MDT) Message-Id: <20081015.102514.796899934.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely7.cicely.de From: "M. Warner Losh" In-Reply-To: <20081015162140.GQ25586@cicely7.cicely.de> References: <20081014.153418.1353606085.imp@bsdimp.com> <18677.7678.159413.615726@gromit.timing.com> <20081015162140.GQ25586@cicely7.cicely.de> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arm@FreeBSD.org Subject: Re: loadable drivers X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2008 16:25:38 -0000 In message: <20081015162140.GQ25586@cicely7.cicely.de> Bernd Walter writes: : On Tue, Oct 14, 2008 at 04:32:30PM -0600, John Hein wrote: : > M. Warner Losh wrote at 15:34 -0600 on Oct 14, 2008: : > > In message: <20081015003842.a2bd682b.stas@FreeBSD.org> : > > Stanislav Sedov writes: : > > : On Tue, 14 Oct 2008 14:25:32 -0600 : > > : John Hein mentioned: : > > : : > > : > What needs to be done to support loadable drivers under arm/freebsd? : > > : : > > : I think they should work, aren't they? : > > : > > Build them... They work.. : > : > Sorry for the poor problem statement. They do load, but I'm not : > getting into the probe or attach. At first I thought the load : > was failing, but that was driver error (pardon the pun). : : Then it is likely a driver or configuration specific problem. : One of the possible reasons is that you may missing hints, because many : devices in embedded systems don't support probing. : IIRC I already successfully loaded USB modules on AT91. The problem, communicated privately, was there's no identify routine, so it never was added to atmelbus so nothing happened when the module was loaded. Warner