Here are some (very) simple Examples of how to access an IOWarrior.
There are a few comments in the sources, but you should read 
IOWarrior-HowTo.txt for more information.

All examples start by opening the device attached to 
/dev/usb/iowarrior0 or /dev/usb/iowarrior1
When an IOWarrior is found all the examples will print the
available device-information.

minimum_read0 :
  Reads a single report from the IO-Pins of the IOWarrior.	      
  If no data is immediatly available, the program will wait for
  10 seconds and then exit. So if you have an Iowarrior-Starterkit,
  simply push the button ....

minimum_write0 :
  Write a single report to the IO-Pins of the IOWarrior.
  You have to provide the bytes to be written as hex-values 
  on the commandline. For an IOWarrior40:
  > minimum_write0 ff ff ff 00
  should light up all the leds on the Starterkit.

get_io_status :
  Send the SpecialMode-fuction "GetCurrentPinStatus" (ReportId=0xff) to
  the IOWarrior and waits for the reply from the device.
  So this is basically an example for reading and writing
  to the SpecialModes of an IOWarrior.

get_io_status_direct :
  Also reads the current IO-Pin-status, but uses an
  usb_control_msg instead of the SpecialMode command.

		      
Compiling :
  Simply 'make'. The Makefile expects "iowarrior.h" in
  the parent-directory of the samples directory. If you relocated
  the header to some other directory, edit the 'MODULE_DIR' variable
  in the Makefile.


