From owner-freebsd-current@FreeBSD.ORG Mon Jan 10 05:53:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D2B016A4CE; Mon, 10 Jan 2005 05:53:04 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F45A43D1F; Mon, 10 Jan 2005 05:53:04 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 412B2651EE; Mon, 10 Jan 2005 05:53:03 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 58351-03; Mon, 10 Jan 2005 05:53:02 +0000 (GMT) Received: from empiric.dek.spc.org (unknown [213.210.24.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 7F3C4651EB; Mon, 10 Jan 2005 05:53:02 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id A0E746530; Mon, 10 Jan 2005 05:53:09 +0000 (GMT) Date: Mon, 10 Jan 2005 05:53:09 +0000 From: Bruce M Simpson To: Julian Elischer Message-ID: <20050110055309.GG709@empiric.icir.org> References: <200501090750.j097oXj0020917@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501090750.j097oXj0020917@freefall.freebsd.org> cc: current@FreeBSD.org Subject: Re: got a "ucom" or "usio" device? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 05:53:04 -0000 On Sun, Jan 09, 2005 at 07:50:33AM +0000, Julian Elischer wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/73799 > can you test the patch supplied above for your device? Apologies as this isn't directly related to this specific change, but the nature of the change. I think moving things out of usbd.conf is a good thing (as devd is a more general way of doing many of the things which usbd does). However, I should like to know how to go about converting the following usbd.conf entries to devd.conf and perhaps committing it, together with a port, for the convenience of those of us who use Bluetooth together with the rather common Broadcom chips which need firmware: %%% # Firmware download for Broadcom BCM2033 Bluetooth dongle. # # Requires that the ubtbcmfw.ko module is pre-loaded in order for the # pre-firmware device to be recognised. ng_ubt.ko should be pre-loaded # also, in order for the device to be connected to the Bluetooth stack. # # The firmware image files are not installed by default and should be # extracted from the Linux BlueZ firmware collection at: # http://www.bluez.org/download.html # device "Broadcom BCM2033 Bluetooth dongle" devname "ubtbcmfw[0-9]+" attach "/usr/sbin/bcmfw -n ${DEVNAME} -m /usr/local/share/usb/firmware/B CM2033-MD.hex -f /usr/local/share/usb/firmware/BCM2033-FW.bin" %%% I imagine something like the following would be required, but would appreciate a quick glance at it:- %%% attach 10 { device-name "ubtbcmfw[0-9]+"; action "/usr/sbin/bcmfw -n $device-name -m /usr/local/share/usb/firmware/BCM2033-MD.hex -f /usr/local/share/usb/firmware/BCM2033-FW.bin"; }; %%% Regards, BMS