Date: Sat, 18 Jul 2020 07:01:07 +0200 From: Hans Petter Selasky <hps@selasky.org> To: "Brian Mcgovern (bmcgover)" <bmcgover@cisco.com>, Ian Lepore <ian@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Question on structure of USB (specifically USB Serial) stack Message-ID: <4504811e-9eed-d3a1-8d5e-561f7f3ce837@selasky.org> In-Reply-To: <BL0PR11MB344286D12DDD48451E274141C57F0@BL0PR11MB3442.namprd11.prod.outlook.com> References: <BL0PR11MB34425EBBCF3E674E6A7766E1C57F0@BL0PR11MB3442.namprd11.prod.outlook.com> <c20edccb-616b-aedf-6a60-e4857341f2fb@selasky.org> <82c1e5cede57ced764bfc3a33c75cc0b36a67660.camel@freebsd.org> <BL0PR11MB344286D12DDD48451E274141C57F0@BL0PR11MB3442.namprd11.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-07-17 01:18, Brian Mcgovern (bmcgover) wrote: > What I'm hoping to do is pin some USB devices with FTDI interfaces to more consistent name, similar to /dev/usb, based on the tree of struct usb_device entries and their respective addresses. You might get some ideas how to get struct usb_device inside ucom, by looking at this differential revision: https://reviews.freebsd.org/D21886 Basically you need to make a new API which is passed the uaa->device pointer. Then no void * casting will be needed. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4504811e-9eed-d3a1-8d5e-561f7f3ce837>