From owner-freebsd-usb@FreeBSD.ORG Thu Aug 21 18:07:09 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 938C8106568A for ; Thu, 21 Aug 2008 18:07:09 +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 290348FC23 for ; Thu, 21 Aug 2008 18:07:08 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=fyLvYZp7xZAA:10 a=BbDwgmqKlHIA:10 a=6MIg2jpqvhTpo/gR8GzG7Q==:17 a=lqGwVcz9kNzltA7ObZcA:9 a=WCjZRPY8LiIybvBY3d0A:7 a=SSKbopsvdwRBJ7mfdZ_BU5VA41QA:4 a=LY0hPdMaydYA:10 Received: from [62.113.133.243] (account mc467741@c2i.net [62.113.133.243] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1052523031; Thu, 21 Aug 2008 20:07:07 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Thu, 21 Aug 2008 20:08:48 +0200 User-Agent: KMail/1.9.7 References: <48ADA51C.5020107@telenix.org> In-Reply-To: <48ADA51C.5020107@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808212008.50544.hselasky@c2i.net> Cc: Subject: Re: trying out the new usb stuff ... 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: Thu, 21 Aug 2008 18:07:09 -0000 On Thursday 21 August 2008, Chuck Robey wrote: > I'm not sure how to change my config to try out the new usb2 code. I saw > where you mentioned the new config lines, but I'm not sure what to do with > the devices I have in my kernel now (I don't use the modules for usb). I > mean, things like usb, ohci, ehci, etc., do you keep them in or change them > (and what's the complete list of required changes, not only the additions?) Hi Chuck, 1. Remove all the USB modules from the kernel config. 2. Add this to your /boot/loader.conf after installing the patches and building a new kernel. usb2_core_load=YES usb2_controller_load=YES usb2_input_load=YES > Lastly, are there any changes contemplated in the usb hid code? I'm not > sure if it's my own ineptness, or bugs in the usbhid code, but there are > parts of that libhibhid code that I've never been able to get to work (I > needed to write my own), so I'm really interested if the usbhid stuff is > going to change or not. Yes, there are some new IOCTLs which might solve some of your problems. /* Generic HID device */ #define USB_GET_REPORT_DESC _IOR ('U', 21, struct usb2_gen_descriptor) #define USB_SET_IMMED _IOW ('U', 22, int) #define USB_GET_REPORT _IOWR('U', 23, struct usb2_gen_descriptor) #define USB_SET_REPORT _IOW ('U', 24, struct usb2_gen_descriptor) #define USB_GET_REPORT_ID _IOR ('U', 25, int) struct usb2_gen_descriptor { void *ugd_data; uint16_t ugd_lang_id; uint16_t ugd_maxlen; uint16_t ugd_actlen; uint16_t ugd_offset; uint8_t ugd_config_index; uint8_t ugd_string_index; uint8_t ugd_iface_index; uint8_t ugd_altif_index; uint8_t ugd_endpt_index; uint8_t ugd_report_type; uint8_t reserved[8]; }; For UHID you only need to initialise ugd_data, ugd_maxlen and ugd_report_type . --HPS