Re: USB drivers

From: M. Warner Losh (imp_at_bsdimp.com)
Date: 08/07/04

  • Next message: Darren Pilgrim: "RE: USB drivers"
    Date: Sat, 07 Aug 2004 15:59:20 -0600 (MDT)
    To: dmp@bitfreak.org
    
    

    In message: <000001c47cb8$8ef1bb50$142a15ac@spud>
                "Darren Pilgrim" <dmp@bitfreak.org> writes:
    : > From: M. Warner Losh
    : >
    : > In message: <41124C8B.2060902@tellme3times.com>
    : > Chris <chris@tellme3times.com> writes:
    : > :
    : > : What I am trying to determine is why my multifunction
    : printer/scanner
    : > : receives only one of the two drivers. Is it because the printer
    : does
    : > : not respond properly? Is it because the printer is not defined? I
    : > : have many questions here.
    : >
    : > Yes. Usb is a little complicated in this area, and there are a number
    : > of details that are hard to get right. It wouldn't surprise me if the
    : > current set of drivers are less than completely optimal.
    :
    : On a bit of a side-track, I'm wondering if it could be due to how the
    : multifunction device presents itself? A bit back in this thread someone
    : mentioned that a pointer must be present for a driver to attach to a
    : device. If there is only one pointer for a device, only one driver may
    : attach. Since a single USB bus can have a LOT of devices and each
    : device's capabilities are determined through the presence of usage
    : pages, I see two ways for a multifunction device to present itself:
    :
    : - A single device ID with more than one usage page. All the
    : functionality is there and is compatible with FreeBSD drivers, but since
    : there is only one device probed on the bus, only one driver may attach.
    : Perhaps a "simple" mux driver would be useful?
    :
    : - A multiple single-usage device IDs. Same functionality as before, but
    : now FreeBSD can probe unique printer and scanner devices and thus let
    : both ulpt and uscanner attach simutaneously.
    :
    : Am I way off base?

    No. You are exactly on base. That's why I pointed at you at the usb
    information program. Run it with the device plugged in, and we'll be
    able to know the details.

    Warner
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Darren Pilgrim: "RE: USB drivers"

    Relevant Pages

    • Re: USB drivers
      ... :>>From: M. Warner Losh ... :>>: What I am trying to determine is why my multifunction ... :>mentioned that a pointer must be present for a driver to attach to a ... If there is only one pointer for a device, only one driver may ...
      (freebsd-current)
    • RE: USB drivers
      ... What I am trying to determine is why my multifunction ... mentioned that a pointer must be present for a driver to attach to a ... If there is only one pointer for a device, only one driver may ... - A single device ID with more than one usage page. ...
      (freebsd-current)
    • Re: MOUHID attaching problem
      ... driver passes AttachDevice function in CDevice.cpp. ... UHCD driver DLL attach ... InitializeUHCI ++ ... CHub(Root tier 0)::AllocateDeviceArray - attempting to allocate 1 devices ...
      (microsoft.public.windowsce.platbuilder)
    • [PATCH 2.6.10-rc1 0/4] driver-model: manual device attach
      ... These are the manual device attach patches I was talking about in the ... dev.autoattach is read/write integer sysctl node which controls ... driver-model's behavior regarding device - driver association. ...
      (Linux-Kernel)
    • Problems installing X25 9.1 on Solaris 8
      ... Driver successfully added to system but failed to attach ... Warning: Driver successfully added to system but failed to attach ... Installation of was successful. ...
      (SunManagers)