1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-23 11:18:54 +00:00
freebsd/tools
Hans Petter Selasky 8030839bd2 Initial commit of my USB test code which can exercise connected USB
devices and the FreeBSD USB stack itself. This program can be used to
test compliance against well established usb.org standards, also
called chapter-9 tests. The host platform can act as either USB device
or USB host depending on the available hardware. The basic USB
communication happens through FreeBSD's own libusb v2, and some
sysctls are also used to invoke specific error conditions. This test
program can be used to verify correct operation of external USB
harddisks under heavy load and various other conditions. The software
is driven via a simple command line interface. Main supported USB host
classes are "USB mass storage" and "USB modems".
2013-08-09 20:08:42 +00:00
..
bsdbox Do a bunch of fixing and refactoring. 2012-08-29 22:55:50 +00:00
build Adjust make knobs to know that WITH_ICONV installs a /usr/bin/iconv 2013-08-06 21:30:37 +00:00
debugscripts A number of places in the source tree still reference cuad.* after 2012-12-08 22:16:36 +00:00
diag Remove scripts and tools which only functioned when src was using CVS 2012-09-13 17:49:11 +00:00
kerneldoc Correct double "the the" 2012-09-14 21:28:56 +00:00
KSE
LibraryReport
regression Add mkostemp() and mkostemps(). 2013-08-09 17:24:23 +00:00
sched
test This test is working now, so remove it from NOTWORK. 2013-06-02 01:07:38 +00:00
tools Initial commit of my USB test code which can exercise connected USB 2013-08-09 20:08:42 +00:00
install.sh Use = not == in test arguments. 2013-01-24 20:47:37 +00:00
make_libdeps.sh Import libyaml as libbsdyml (private brand name) 2013-03-04 11:27:41 +00:00
README
tinder.sh

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.