Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Dec 2002 13:29:06 +0100
From:      Stijn Hoop <stijn@win.tue.nl>
To:        Bernd Walter <ticso@cicely.de>
Cc:        Brad Hughes <freebsd@thc-cs.ath.cx>, freebsd-current@freebsd.org
Subject:   Re: SCM Microsystems Inc. eUSB SmartMedia Adapter
Message-ID:  <20021213122906.GC64137@pcwin002.win.tue.nl>
In-Reply-To: <20021211183810.GK20338@cicely8.cicely.de>
References:  <3DF6AD6D.8070009@thc-cs.ath.cx> <20021211075812.GA52865@pcwin002.win.tue.nl> <20021211171221.GJ20338@cicely8.cicely.de> <20021211180336.GA55794@pcwin002.win.tue.nl> <20021211183810.GK20338@cicely8.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--s2ZSL+KKDSLx8OML
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 11, 2002 at 07:38:11PM +0100, Bernd Walter wrote:
> On Wed, Dec 11, 2002 at 07:03:36PM +0100, Stijn Hoop wrote:
> > On Wed, Dec 11, 2002 at 06:12:21PM +0100, Bernd Walter wrote:
> > > On Wed, Dec 11, 2002 at 08:58:12AM +0100, Stijn Hoop wrote:
> > > > On Tue, Dec 10, 2002 at 10:13:49PM -0500, Brad Hughes wrote:
> > > > Try to remove device ugen from your kernel; it is a bit agressive w=
hen
> > > > 'claiming' USB devices. I had the same problem with an USB gamepad =
and
> > > > uhid devices.
> > >=20
> > > This shouldn't be possible.
> > > Can you show an example when this happens?
> >=20
> > It used to happen with my Thrustmaster Firestorm Wireless gamepad.
> > At the time I had both uhid & ugen in my kernel, it also happened when
> > I used uhid as a loadable module. It finally worked when I removed
> > ugen from my kernel configuration file, and used the uhid module.
> > I never tested to see whether using uhid in a kernel configuration
> > file (instead of a module) worked because I was happy to get it
> > to play nicely.
>=20
> If the device is attached with only ugen available then of course ugen
> gets it.
> When you load a module later, then the decision about the driver for
> that device has already been made.

Yes I understand.

> But I don't see how this could happen if you already have uhid in
> the kernel.

Well I thought it did -- but upon retesting with an up-to-date -CURRENT,
it works now. Sorry for the false alarm.

--Stijn

--=20
The rain it raineth on the just
	And also on the unjust fella,
But chiefly on the just, because
	The unjust steals the just's umbrella.

--s2ZSL+KKDSLx8OML
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE9+dKSY3r/tLQmfWcRAt17AJ9xe7hVY5svC3143DSR0OIQwNMVWACdH1ew
I/Xm5eWmAXoPiTXa+s4SYfA=
=DzE3
-----END PGP SIGNATURE-----

--s2ZSL+KKDSLx8OML--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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