Hello,
Did anyone make start already making hands dirty? I just did. My first
lines are these:
in unusual_devs.h:
UNUSUAL_DEV( 0x04e6, 0x1010, 0x0000, 0x9999,
"Shuttle",
"SCM USBAT-02",
US_SC_SCSI, US_PR_CB, usbat2_Initialisation, 0),
The first two arguments were not too difficult. The next two should be
bcdDeviceMin and bcdDeviceMax. I wondered what this could be. "bcd"
stands for "binary code data" (for example "2.10" has bcd "0x0210").
Because I don't know any what values should be mentioned here I did just
something. Any better ideas?
The next two arguments have limitations to string length (see usb.c).
The other values I "borrowed" from other definitions. Except
usbat2_Initialisation, which has to be defined in some C-file. I looked
into the Makefile. There I saw:
usb-storage-obj-$(CONFIG_USB_STORAGE_SHUTTLE_COMPACTFLASH) += shuttle_cf.o
And no shuttle_cf.c file was present. So I guess this is the one Matthew
expect us to create?
I created a shuttle_cf.c with a dumme usbat2_Initialisation and decided
to make a new usb_storage.o module and see whether is was possible to
generate a debug message in the logfile when initialisation was triggered.
Therefore I added a few lines to the Makefile in the directory where my
development files are. Something like this:
TOPDIR := /usr/src/linux-2.4
CONFIG_USB_STORAGE := y
CONFIG_USB_STORAGE_SHUTTLE_COMPACTFLASH := y
But typing "make" resulted in an overwelming number of error messages,
all about parsing errors in kernel header files, for example:
/usr/src/linux-2.4/drivers/scsi/scsi.h:582: parse error before `:'
This lines contains: unsigned online:1;
I guess some compile flags should be given to gcc....
Maybe I should proceed in another way.... Suggestions?
Herald