Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Oct 2008 10:25:14 -0600 (MDT)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        ticso@cicely.de, ticso@cicely7.cicely.de
Cc:        arm@FreeBSD.org
Subject:   Re: loadable drivers
Message-ID:  <20081015.102514.796899934.imp@bsdimp.com>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20081015162140.GQ25586@cicely7.cicely.de>
            Bernd Walter <ticso@cicely7.cicely.de> 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 <stas@freebsd.org> writes:
: >  > : On Tue, 14 Oct 2008 14:25:32 -0600
: >  > : John Hein <jhein@timing.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081015.102514.796899934.imp>