From owner-freebsd-usb@FreeBSD.ORG Fri Jan 11 15:05:03 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 CA68D16A476 for ; Fri, 11 Jan 2008 15:05:03 +0000 (UTC) (envelope-from gofdu-freebsd-usb@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 776CE13C4CC for ; Fri, 11 Jan 2008 15:05:03 +0000 (UTC) (envelope-from gofdu-freebsd-usb@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1JDL3C-0002We-EB for freebsd-usb@freebsd.org; Fri, 11 Jan 2008 14:40:02 +0000 Received: from 81.210.234.246 ([81.210.234.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jan 2008 14:40:02 +0000 Received: from saper by 81.210.234.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jan 2008 14:40:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-usb@freebsd.org From: Marcin Cieslak Date: Fri, 11 Jan 2008 15:21:56 +0100 Lines: 36 Message-ID: <47877B84.9050106@system.pl> References: <200801090114.56195@aldan> <200801091015.17730@aldan> <200801102203.m0AM33dF091080@chevy.androcles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 81.210.234.246 User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.11) Gecko/20071215 SeaMonkey/1.1.7 In-Reply-To: <200801102203.m0AM33dF091080@chevy.androcles.org> Sender: news Cc: 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 15:05:03 -0000 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? Did NetBSD do any progress in this area? (I can see their current USB and Bluetooth stacks are more advanced then ours). And what wonders me most - we are lucky if we end up with a standard tty or storage interface in the end, but what userland interface should we give for example to SANE? sanei_usb interface defines : "usb_write_bulk", that goes as a simple write() to our /dev/uscanner, "usb_read_bulk" - simple read(), "usb_read_int" (not supported with /dev/uscanner), "usb_control_msg" that sends a message to a control pipe (USB_DO_REQUEST of ugen, available to uscanner only if you patch it). My scanner (HP3300C) needs to talk to the control pipe to read/write its registers for example. --Marcin