Quoting Chuck Robey <chuckr_at_chuckr.org> (Tue, 12 Feb 2008 15:53:13 -0500): > But, I guess there's been a lot of coding in usb, because the state of usb > docs is, well, mostly missing in action. I found about a conf file in /etc > called usbd.conf, but I would guess that's a goner too (although this is a > recently installed machine, so it shouldn't be too chock full of ancient > memorabilia. cd /usr/src make check-old make delete-old make delte-old-libs (make sure you don't need them anymore) > The handbook, both the regular version AND the developer version, treat usb > only from the direction of masss storage. Once I get to the point of > understanding this data dump I have (and that won't bee all that long) I > need more into about how to architecturally amke this work. Questions > like, does this item need to operate alone, or along with my current > trackball? If I write a device driver for this, what kind of interface > should I present at /dev? If I get this done, will I just enter some You could ask hps_at_FreeBSD.org, he is working on a new USB stack in perforce. Bye, Alexander. -- "Look at that five o'clock rust. You've been up all night not drinking, haven't you?" -Leela http://www.Leidinger.net Alexander _at_ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild _at_ FreeBSD.org : PGP ID = 72077137Received on Sat Feb 16 2008 - 10:18:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:27 UTC