Date: Fri, 29 May 2009 10:13:02 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Andrew Thompson <thompsa@freebsd.org> Subject: Re: ugen and newbus Message-ID: <200905291013.03870.hselasky@c2i.net> In-Reply-To: <20090528222630.GF74376@citylink.fud.org.nz> References: <20090528222630.GF74376@citylink.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 29 May 2009, Andrew Thompson wrote: > Hi, > > > On the new usb stack the ugen driver attaches to all usb devices and > generates a devd attach event but doesnt actually have a device entry. > > It either needs to be a device or use a different devd notification. It > would be easier if it was a device as that takes care of the housekeeping. > > I am not sure that the best way to attach it into the device tree, a > ugen device represents a physical unit and may have multiple usb drivers > attach (like a 3g device with a built in sd reader). > > ehci0 > usbus0 > uhub0 > umass0 > umass1 > uhub1 > u3g0 > umass2 > uplcom0 > uplcom1 > > This would become > > ehci0 > usbus0 > ugen0 > uhub0 > ugen1 > umass0 > ugen2 > umass1 > ugen3 > uhub1 > ugen4 > u3g0 > umass2 > ugen5 > uplcom0 > ugen6 > uplcom1 > > Is that the right way to do it? > Hi, In other words, you want to wrap "struct usb_device" into "device_t". Attaching ugenX.Y would then be a replacement for enumerating a device. Or do you just want to create a dummy device? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905291013.03870.hselasky>