A short document for whomever continues this project. by: Josh Huber --------------------------------------------- /---\ |TOC| \---/ 1. Development Machine Setup 1.1 CVS 1.2 Apache/cvsweb 1.3 root password (changeme!) 2. Files 3. Driver Status 4. Additional Help ********************************* * 1. Development Machine Setup Important things to know about the development machine (fibre-penguin.wpi.edu) are: 1.1 CVS repository is located at /usr/local/cvs To checkout: Add a user for yourself on the system (see 1.3), and add yourself to the 'cvs' group. Then, from another machine: $ cvs -d login $ cvs -d co fp Where in the above commands is: :pserver:@fibre-penguin.wpi.edu:/usr/local/cvs This will create a directory called 'fp' which contains the emulexfc driver source code and makefile (see section 2) You might want to get familiar with cvs at the point. (check out http://www.loria.fr/~molli/cvs-index.html), but basically, what you do is the following (after you have logged in and checked out the source, you needn't use the -d syntax any more): cd cvs up # updates your source with any changes ....hack...hack...hack... cvs commit # cvs will now ask you for a text description of your changes. There is also a fp-doc repository with all sorts of fibre channel, emulex, and clariion documentation. I highly reccommend checking it out. 1.2 Apache/cvsweb There is a web server set up, with html in /var/www (default Debian location), with project information. Also, I installed cvsweb, so that you can view the driver progress from the web page. You can also get diffs between any two versions via the web page. It might be a good idea to move the CVS and web server off the development machine. 1.3 root password You'll need this. (See the README-REAL) * 2. Files There are really only 2 files that contain the emulexfc driver, the c file (emulexfc.c) and the header file (emulexfc.h). Pretty standard for a Linux driver. The supplied Makefile is a total hack (tip: read it for a good laugh!), and should be fixed, so as to support building outside of a kernel tree using a -I/path/to/kernel/includes and the appropriate defines. Adding the required changes to Documentation/Configure.help, drivers/scsi/Config.in, and drivers/scsi/Makefile would also be a good idea if you were instead move the source files into the kernel tree itself. It's up to you. 3. Current Driver Status. I recommend reading the last chapter of our MQP report to find out where we left off. Also, take a look at the methodology and driver chapters for some slides that may help you out. 4. Additional Help Feel free to email myself, or my partner John at: Josh Huber John Baboval Good luck!