> > > P.S.: USBDI as in, our version of it. The people from the consortium
> > > kicked us out.
>
> > Can you elaborate on the reason that USBDI does not FreeBSD
> > to be involved with the consortium?
>
> Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
> consortium. N
> > > P.S.: USBDI as in, our version of it. The people from the consortium
> > > kicked us out.
>
>
> > Can you elaborate on the reason that USBDI does not FreeBSD
> > to be involved with the consortium?
>
> Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
> consortium
> > P.S.: USBDI as in, our version of it. The people from the consortium
> > kicked us out.
> Can you elaborate on the reason that USBDI does not FreeBSD
> to be involved with the consortium?
Money. We cannot pay the fee (>1000 US $) to join the kindergarten aka
consortium. No company was w
>
> P.S.: USBDI as in, our version of it. The people from the consortium
> kicked us out.
Can you elaborate on the reason that USBDI does not FreeBSD
to be involved with the consortium?
Tnks
P.S.: Just got a 3 COM USB modem and I am going over the USB specs right now 8)
--
Amancio
Currently we have the following:
- working drivers for keyboards, mice, hubs
- usable driver for USB Zip drive (Iomega, SCSI) (any
coders/testers (the true combination) welcome)
I am currently finishing the initial workings of the Zip driver and have
been able to MSDOS fo
Redirected to -current...
I seem to recollect that you were having problems in handling interrupts so
were are
you at with this problem..
>
> Unplug a few devices and you will have the opportunity to review the
> devices probed in your machine (reboot).
>
> I've only removed the list
