From owner-freebsd-usb@FreeBSD.ORG Fri Jan 11 18:10:01 2008 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2880B16A418 for ; Fri, 11 Jan 2008 18:10:01 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id AE31013C468 for ; Fri, 11 Jan 2008 18:10:00 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.45] (account mc467741@c2i.net [85.19.218.45] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 771187731; Fri, 11 Jan 2008 19:09:58 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 11 Jan 2008 19:10:40 +0100 User-Agent: KMail/1.9.7 References: <200801090114.56195@aldan> <200801102203.m0AM33dF091080@chevy.androcles.org> <47877B84.9050106@system.pl> In-Reply-To: <47877B84.9050106@system.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801111910.41509.hselasky@c2i.net> Cc: Marcin Cieslak , Mikhail Teterin Subject: Re: BlackBerry (Re: using libusb) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 18:10:01 -0000 On Friday 11 January 2008, Marcin Cieslak wrote: > Duane H Hesser wrote: > >> The only work-around is to not have umass, etcetera in your kernel, > >> but that sucks, because one may want to be able to access /some/ > >> devices as mass-storage, and some others as merely generics... > > > > A similar problem occurs to many of us who have HP printers which > > hook up (quite properly, it seems to me) on ulpt0. Mine also > > hooks up on umass0 (to service the flash memory card slots), > > and would hook up on uscanner0, too, if uscanner.c were modified > > to recognize it. If we want to use HP's software (HPLIP) > > to drive the printer we must arrange arrange for it to be ugen. > > Maybe we should move to the model where we attach drivers to interfaces > or even particular endpoints? What about sharing the control endpoint? Hi, The control endpoint is already shared and we do already support per interface driver attach. What is missing is some glue between userland and the USB kernel. Extending my previous idea: /dev/usb... If the iface is 255 then the iface number is ignored, and we are opening a raw endpoint. Only the super user is allowed to do this. Else the rule becomes that endpoints on an interface can only be opened when no other kernel driver is attached to that particular interface, unless you are super user. What do you think ? --HPS