I will try and take a look at this later today. I know we went over this once before, but I'll say it again -- I really think writing kernel drivers is the wrong approach. All my code just runs as root and uses iopl() to allow access to the io ports for polled A/D and the parallel port for actuators.
Minimizing build and install complexity is a Good Thing. I don't advocate breaking code up into libraries for this project, either. My flight control software has a very simple layout, and a five line makefile: flightcom.c - flight computer main loop flightcom.h - flight computer private definitions misc.c - a few common routines for dealing with serial devices flightcontrol.c - shared code between flight computer and simulator flightcontrol.h - shared definitions between flight computer and simulator garmin.c - gps adc.c - a/d board usbjoystick.c - linux usb joystick serialjoystick.c - wingman warrior RS232 joystick xbow.c - crossbow inertial unit altimeter.c - laser atlanta altimeter tcm2.c - precision navigation magnetometer / inclinometer (not used at the moment) John Carmack _______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
