Below is information on how you can help out the team with testing
of the rt2400 kernel module.

1. Get the latest source from the CVS tree. Easiest way todo this is to
sign up to SourceForge and then use the commands below to get the current
mainline source (as last time I checked anon-cvs was not working 100%)

export CVS_RSH=ssh
cvs -d:ext:username@cvs.sf.net:/cvsroot/rt2400 co source

2. Enable module debugging. Todo this run 'make clean' to remove any
compiled objects you have and then run 'make debug; make install'.
This will recompile the Module with debugging turned on and reinstall
it over your existing module. 

3. Compile and install the module as per the INSTALL instructions.

4. Load the module with full debug enabled using the command
	modprobe rt2400 debug=5

5. Any bugs/issues you find please report the following information
to the rt2400-devel mailing list
	* Steps to reproduce
	* The last few lines of your debugging output which should go
          through syslog and end up somewhere like /var/log/messages
          or /var/log/debug (depending on your syslog config)
	* Your hardware architecture (i.e. x86, AMD64, Sparc)
	* Your kernel version (i.e. 2.4.25 or 2.6.4)
	* Your rt2400 hardware manufacturer and model
	* Anything else you may think will help us resolve the issue
	  (even a patch if you are so inclined)

5. Sign up to the rt2400-devel mailing list and watch out for requests
for testing. Whenever we do major changes to the source and always
just before a release we will call for testing to be done before we
make the general release. 
