Date: Thu, 13 Nov 2003 15:41:31 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Dag-Erling Smorgrav <des@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/moused moused.c Message-ID: <20031113153949.O82404@carver.gumbysoft.com> In-Reply-To: <200311132125.hADLPCUC056661@repoman.freebsd.org> References: <200311132125.hADLPCUC056661@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Nov 2003, Dag-Erling Smorgrav wrote: > If the name of the mouse device starts with "/dev/ums", try to load the > ums module, and allow for up to five attempts to open the device, with > two-second pauses in between, to allow time for USB controllers and > devices to probe and attach. My Gigabyte P4 Titan 848P motherboard has > a total of 15 ports on four hubs hanging off four controllers, and needs > at least half of that ten-second allowance to get ready. This is only a problem if you don't have ums in your kernel or loaded as a module. On attach usbd launches moused in the default configuration. ums ships in GENERIC and usbd is enabled by default, so this seems to be introducing a kludge for your own broken configuration. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031113153949.O82404>