Building and testing the source

As soon as you've checked out the source, you should move this source into a Haiku-cvs tree, at the locations where they should be. That means that the bus_manager source should be located at current/src/add-ons/kernel/bus_managers/usb and the busses source should be located at current/src/add-ons/kernel/busses/usb. Clear these directories before you place the freshly checked out source in it (or simply remove those directories and move the checked out source to those locations). As long as there isn't a CVS subdirectory, you won't get into trouble when CVS-updating.

To build the stack, simply perform a jam usb uhci in the root of the Haiku cvs tree (current/). In the current/distro subtree the binaries will be placed. In order to actually try the stack, two steps are needed. First, make sure you have no usb mouse or keyboard. You'll be unable to use those. If you fulfill that requirement, you should move the usb and uhci modules, from the /boot/beos/system/add-ons subdirectories (this follows the same naming standards as the haiku source tree). Then place your fresh binaries into those exact locations.

Currently, my USB stack implementation doesn't have the same module signature as Be's. In order to actually load the stack, you should download a fake driver, called usbtest. Try tla get usbtest--mainline--0.1. Build the thing with BeIDE, and place it in /boot/home/config/add-ons/kernel/drivers/bin, and symlink it in /boot/home/config/add-ons/kernel/drivers/dev/misc/. Finally (after a restart, probably), you'll be able to open the driver (I use python), and if you watch the syslog output, you should see what's happening.