Yes I realise that, I was trying to use the c860 binary and I didn\'t even get that far. After compiling the code I\'ve at least got a disk drive showing, and looking at the source I\'ve not actually changed anything in particular (ie the defines all seem to give the same numbers) so I was hopeful that I might be able to get further once I work out what I did actually change.
How did you get the module to compile? Did you compile the C860 kernel source after making alterations to the defconfig (or whatever menuconfig produces) file? I was trying to import the module into the OE (Openzaurus build system) kernel but it refuses to be compiled. In the end I had to look at the compile log when I built the OZ kernel and copy the arm-linux-gcc calls for building net_fd.o and adapt paths, etc.
It\'s a bit difficult to compare the differences between the c860 source and the 5500 source as all of the extra pxa stuff is in there. I\'ve got a quick test script which I\'ll ask someone with a 5600 to run. I hope that it won\'t work, then I can compare the 5600 kernel with the c860 kernel (which should be closer) and see whether I can work out the differences. I\'ll post that in a separate thread though with a more descriptive title.
Si
P.S. @mitch:
with only the supplied drivers for my Zaurus
- exactly, with usb mass storage you don\'t need any drivers, you just plug in and WinXP/2K and Linux will automagically recognise the device and allow you to read/write to it. This means that you don\'t have to carry around a CD with the drivers on it, etc.