Original Makefile has been scrapped. I spent a few hours trying to get the kernel to compile locally on the raspberry pi. Eventually I realized the that the PWD syntax in the makefile copied from the original ServoBlaster repo was not printing the current working directory. Basically, the makefile was making modules for the entire linux distro without compiling the servoblaster.c file into the .ko file needed.

The Makefile is now being created incrementally from scratch.
It now correctly targets the servoblaster.c file and compiled using
the source linux directory on my laptop which was where the kernel
that is booting the Raspberry Pi was originally compiled
Updated Makefile clean command to actually work. Also modified servoblaster.c to have the correct GPIO pin mappings for a revision 2 raspberry pi.

It should be made so that the GPIO mappins are automatically
set so that this line of code does not need to be manually changed.
Made a new bash script to take care of creating the device node for the servoblaster kernel module. Using this script I was successfully able to load the kernel version of the Servoblaster module. Servos attached to the GPIO pins were indeed able to move and respond to different pulse widths.
Added a new table structure to redirect the servo number so that they may be dynamically changed.
Deleted the index table made in the last commit. The read operation has been updated to show the GPIO's that are mapped to each P1 header pin. Also, a few printk's have been added in the cleanup function. I have noticed that unloading the module occassionally causes the raspberry pi to kill the ssh connection and hang. I suspect that the long msleeps being used have something to do with this.
Multiple changes made. A parsing function has been added to get the desired servos from module parameters. Also, the index2servo table has been added again to allow the user to select a specific number of servos for use.
The parsing function for the module parameters that set the GPIO's that will be used has now been tested and is functional.
Change the init functions to use the parse_pins function correctly. If there is a bad input, it default to the first 8 GPIO pins list in the servo2gpio table. The next commit is going to set the system up for all of the available 17 GPIOS on the board, so good chance this version will be reverted back to.
Updated the Read, and init functions of the module. The module is now capable of using selecting which pins the user wants to use. This has been tested for exactly 8 pins. The order of the pins can be reversed or changed in whatever way the user wants and the driver seems to still function.
The module has now been tested to work with different numbers of control pins. It can claim up to 17 GPIO's. I tested the driver using used 2 header pins with the motors provided for testing and the timings seemed accurate. I did not encounter any errors and did not have problems moving the motors around. I then tested the module using 11 GPIO channels. This also seemed to work. At this point, this particular feature for this module has not been tested thoroughly. The problem is that in order to know that the driver is working correctly with all of the different channels enables we need to have a device plugged into all of the GPIO's being used to be able to monitor the pulse timings as well as to make sure that high-voltage signals are being sent down those lines. Theoretically though, the device looks like it's working.
Added dynamic options for Raspberry Pi Revisions. Also added IOCTLs to change some of the module paramters.