On Mon, 19 Apr 1999, Amancio Hasty wrote:
> Insert your e-mail message in your web page under a section titled such as
> Project Status.
Good idea.
> What specifically is needed in the driver to unplug and plug a device?
attach is straightforward.
detach requires:
- disconnect function to handle the fact that the device
does no longer respond (intr context)
- detach function to delete the device and all its
resources (normal context)
- driver unload (detach all drivers)
Currently the problem lies in the fact that free()/malloc() is called
from intr context, resources are completely freed, ongoing transfers are
cleaned away, etc.
Nick
>
>
> >
> > 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 format a disk and been able to read a hfs (iMac)
> > floppy as well. But the driver panics the system when drive unplugged.
> >
> > Planned is:
> >
> > - rewrite of the uhub driver to completely follow newbus
> > (up to now a mixed approach which fails at detach)
> > - start working on 3COM modem support
> > - start working on Ye-Data drive support
> > - start working on Digi 2/4/8 serial port device support
> > - start working on 3COM ISDN adapter support
> > - start working on audio support
> >
> > and while doing this:
> >
> > - solidify the UHCI controller support
> > - solidify the OHCI controller support
> > - improve USBDI
> >
> > The ISDN TA, the Ye-Data drive and Digi serial port device have kindly
> > been provided to me (have not yet arrived though) by the respective
> > hardware vendors. Cherry has provided me with a keyboard (with internal
> > bus powered hub).
> >
> > Anyone care to join? Pick up something fairly straightforward like the
> > audio (Audiocontrol driver). Follow the specs and mail me your comments
> > on the USBDI interface we use. A template driver is the ums mouse
> > driver.
> >
> > Kind regards,
> >
> > Nick Hibma
> > FreeBSD USB project
> > [email protected]
> > http://www.etla.net/~n_hibma/usb/usb.pl
> > http://www.usb.org/
> >
> > P.S.: USBDI as in, our version of it. The people from the consortium
> > kicked us out.
> >
> > On Mon, 19 Apr 1999, Amancio Hasty wrote:
> >
> > >
> > > 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 of devices from GENERIC & LINT, not from the
> > > > conf/files and options. Hiding it basically.
> > > >
> > > > Nick
> > > >
> > > > On Mon, 19 Apr 1999, Amancio Hasty wrote:
> > > >
> > > > > Curious why is USB not ready for public consumption?
> > > > > Got a USB only system : keyboard + mouse working over here.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Amancio Hasty
> > > > > [email protected]
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > e-Mail: [email protected]
> > > >
> > >
> > > --
> > >
> > > Amancio Hasty
> > > [email protected]
> > >
> > >
> > >
> >
> > --
> > e-Mail: [email protected]
> >
>
> --
>
> Amancio Hasty
> [email protected]
>
>
>
--
e-Mail: [email protected]
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
