The following patch was applied to /sys/dev/usb/ugen.c in order to enable
multiple access to the control port:
--- ugen.c.orig 2005-05-16 02:46:59.0 +0930
+++ ugen.c 2005-05-16 03:18:59.0 +0930
@@ -333,14 +333,14 @@
if (sc == NULL || sc->sc_dying)
retu
On Sun, Oct 09, 2005 at 02:38:39PM -0500, LRK wrote:
>
> My test machine has an Intel 82801DB chip which claims to provide USB 2.0
> support for all six USB ports. FreeBSD, however, installs the uhci driver
> rather than ehci. The ehci/usb module shows to be loaded and the Intel
> chip found but a
This is not encouraging:
EHCI(4)FreeBSD Kernel Interfaces ManualEHCI(4)
NAME
ehci -- USB Enhanced Host Controller driver
SYNOPSIS
device ehci
DESCRIPTION
The ehci driver provides support for the USB Enhanced Host Controller
Interface, which
On Sun, Oct 09, 2005 at 11:26:31AM -0700, William Moerner wrote:
> How do you pass critical command line options like
>
> --enable-maintainer-mode
> --with-boost_include-dir=/usr/local/include/boost-1_33/
>
> to this command line, the recommended one for build from CVS?
>
> $ ./for-all-dirs
How do you pass critical command line options like
--enable-maintainer-mode --with-boost_include-dir=/usr/local/include/boost-1_33/
to this command line, the recommended one for build from CVS?
$ ./for-all-dirs ../buildit 2>&1 | tee make.log
Thanks, Weo WN6I
__
On Sun, May 15, 2005 at 10:13:03AM +0930, Berndt Josef Wulf wrote:
> >
> > This is similar to the problem I had with the audio device that doesn't
> > permit it to be opened by two or more processes, see the lines containing
> > EBUSY. I will try to figure out which part of benchmark_usb.py doesn't
On Sun, 9 Oct 2005 12:48, Eric Blossom wrote:
>
>
> I've got a couple of questions:
>
> (1) Is "ham" the proper place for this? Is there something broader
> than "ham" that includes "comms" in general? The majority of our users
> aren't hams, and many of the applications have nothing to do with
>
