Hi all, When starting to develop a USB device driver for a custom device I based this driver on the usb_skeleton.c found in the source tree. Unfortunately I'm having problems to get devfs to work properly on my SuSE 9.0 based PC. So I switched back to a kernel without devfs support.
My question now is, when removing the devfs support from the skeleton_driver, what should I put there instead? I know, that I have to do a mknod for my devices. But I assume, that I have to do something like registering my fops structure with the kernel. What I did was, successfully registering with the usb susbystem, but can I assume that the fops structure is properly propagated to the kernel? I tested with a small usermode program (doing an open(), read(), write() on /dev/mydevice0). All fops functions are called, but the associated device information seems to be lost somewhere. So when doing a write() I end up with a coredump due to accesing some NULL pointer. Could someone please give me a better understanding of how a "non-devfs" based usb driver interacts with usermode programs. I suspect that my problem is related to this part. Thanks a lot, regards, - Andy ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
