From owner-freebsd-usb@FreeBSD.ORG Wed Jan 31 23:47:41 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1B6816A403 for ; Wed, 31 Jan 2007 23:47:41 +0000 (UTC) (envelope-from steinarh@pvv.ntnu.no) Received: from decibel.pvv.ntnu.no (decibel.pvv.ntnu.no [129.241.210.179]) by mx1.freebsd.org (Postfix) with ESMTP id 833E013C471 for ; Wed, 31 Jan 2007 23:47:39 +0000 (UTC) (envelope-from steinarh@pvv.ntnu.no) Received: from bacchus.pvv.ntnu.no ([129.241.210.178]) by decibel.pvv.ntnu.no with smtp (Exim 4.60) (envelope-from ) id 1HCOZs-0003vT-NB for freebsd-usb@freebsd.org; Thu, 01 Feb 2007 00:09:21 +0100 Received: (qmail 49503 invoked by uid 30273); 31 Jan 2007 23:09:20 -0000 Date: Thu, 1 Feb 2007 00:09:20 +0100 From: Steinar Hamre To: Alexander Leidinger Message-ID: <20070131230920.GA45997@pvv.ntnu.no> References: <200701100050.l0A0oOTY002615@freefall.freebsd.org> <20070129203852.2f3d6a89@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070129203852.2f3d6a89@Magellan.Leidinger.net> User-Agent: Mutt/1.4i Cc: bug-followup@FreeBSD.org, freebsd-usb@freebsd.org Subject: Re: kern/107665: [usb] [patch] uscanner support for epson stylus DX5050 MFP 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: Wed, 31 Jan 2007 23:47:41 -0000 On Mon, Jan 29, 2007 at 08:38:52PM +0100, Alexander Leidinger wrote: > Quoting Steinar Hamre (Wed, 10 Jan 2007 00:50:24 GMT): > > > I have reworked the uscanner module so that it can use the device > > simultaniously with the ulpt and umass modules. > > This panics my system at boot time probing. I think my scanner is not > the first interface of the device. uscanner has never supported attaching to other than the first interface on the device. This is hardcoded in USB_ATTACH(uscanner) and is not changed by my patch. Do you have a plain scanner or a multi function device? (What is the product number or output of usbdevs -av?) Did the device work without my patch? If your scanner previosly worked, the only reason I can think of is that your scanner needs usbd_set_config_no. If this is widespread for pure scanner devices, I may rework the patch to be able to attach to both devices and interfaces and use usbd_set_config_no if it did grab the entire device. The concept of set_config_no breaks all multi function devices. Steinar