Browse files

Initial revision

  • Loading branch information...
Thomas Sailer
Thomas Sailer committed Feb 20, 2004
0 parents commit cd35e0d38c8a43df155bdcb52f2a5f01b62461fa
Showing with 27,049 additions and 0 deletions.
  1. +2 −0 AUTHORS
  2. +340 −0 COPYING
  3. +40 −0 ChangeLog
  4. +182 −0 INSTALL
  5. +19 −0
  6. +716 −0
  7. +2 −0 NEWS
  8. +2 −0 README
  9. +861 −0 aclocal.m4
  10. +951 −0 config.guess
  11. +80 −0
  12. +955 −0 config.sub
  13. +5,317 −0 configure
  14. +75 −0
  15. +423 −0 depcomp
  16. +335 −0 devtree.c
  17. +87 −0 devtree.h
  18. +731 −0 getopt.c
  19. +129 −0 getopt.h
  20. +176 −0 getopt1.c
  21. +251 −0 install-sh
  22. +105 −0 list.h
  23. +93 −0 lsusb.8
  24. +1,692 −0 lsusb.c
  25. +3,017 −0 ltconfig
  26. +5,064 −0
  27. +190 −0 missing
  28. +40 −0 mkinstalldirs
  29. +706 −0 names.c
  30. +50 −0 names.h
  31. +1 −0
  32. +3,357 −0 usb.ids
  33. +193 −0 usbdevice_fs.h
  34. +141 −0 usbmisc.c
  35. +36 −0 usbmisc.h
  36. +135 −0 usbmodules.8
  37. +443 −0 usbmodules.c
  38. +51 −0 usbmodules.h
  39. +61 −0 usbutils.spec
@@ -0,0 +1,2 @@
+Thomas Sailer, <>
+Johannes Erdfelt

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -0,0 +1,40 @@
+2000-11-06 Thomas Sailer <>
+ * names.c, lsusb.c: Fixup of Gunther Mayer's patch; do not export
+ internal storage arch out of names.h; formatting beautification;
+ fixed several memory leaks and scribbles
+2000-11-05 Gunther Mayer <>
+ * lsusb.c: Hub Descriptor decode
+ * usb.std: New
+ * lsusb.c: HID Report Descriptor decode
+ * lsusb.c: String Descriptors w/ LANGID, assume Unicode-ASCII for the moment
+2000-11-03 Adam J. Richter <>
+ * lsusb.c: Retry usb_control.
+1999-12-03 Thomas Sailer <>
+ * lsusb.c: bogus error checks for open calls, reported by Matthew Darm
+1999-09-17 Thomas Sailer <>
+ * bumped version number.
+ * usbutils.spec: likewise.
+ * names.c: added parsing routines for terminal types to be listed in usb.ids
+ * names.h: likewise.
+ * lsusb.c (dump_audiocontrol_interface): likewise.
+1999-09-16 Thomas Sailer <>
+ * lsusb.c (dump_audiocontrol_interface): fixed a couple of forgotten printf arguments
+1999-09-13 Thomas Sailer <>
+ * Created package
@@ -0,0 +1,182 @@
+Basic Installation
+ These are generic installation instructions.
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+ The file `' is used to create `configure' by a program
+called `autoconf'. You only need `' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+The simplest way to compile this package is:
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system. If you're
+ using `csh' on an old version of System V, you might need to type
+ `sh ./configure' instead to prevent `csh' from trying to execute
+ `configure' itself.
+ Running `configure' takes awhile. While running, it prints some
+ messages telling which features it is checking for.
+ 2. Type `make' to compile the package.
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+Compilers and Options
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. You can give `configure'
+initial values for variables by setting them in the environment. Using
+a Bourne-compatible shell, you can do that on the command line like
+ CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+Or on systems that have the `env' program, you can do it like this:
+ env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+Compiling For Multiple Architectures
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+ If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory. After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+Installation Names
+ By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+Optional Features
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+Specifying the System Type
+ There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on. Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+ If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+Sharing Defaults
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/' if it exists, then
+`PREFIX/etc/' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+Operation Controls
+ `configure' recognizes the following options to control how it
+ Use and save the results of the tests in FILE instead of
+ `./config.cache'. Set FILE to `/dev/null' to disable caching, for
+ debugging `configure'.
+ Print a summary of the options to `configure', and exit.
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+`configure' also accepts some other, not widely useful, options.
@@ -0,0 +1,19 @@
+sbin_PROGRAMS = lsusb usbmodules
+noinst_HEADERS = names.h usbdevice_fs.h devtree.h list.h usbmodules.h usbmisc.h
+lsusb_SOURCES = lsusb.c names.c devtree.c usbmisc.c
+lsusb_LDADD = @LIBOBJS@
+usbmodules_SOURCES = usbmodules.c usbmisc.c
+usbmodules_LDADD = @LIBOBJS@
+data_DATA = usb.ids
+man_MANS = lsusb.8 usbmodules.8
+EXTRA_DIST = $(man_MANS) $(data_DATA) usbutils.spec getopt.h getopt.c getopt1.c
Oops, something went wrong.

0 comments on commit cd35e0d

Please sign in to comment.