On Mon, 18 Oct 2004, Ethan Mattor wrote: > Hello, > > I have also been working with the usb-skeleton.c file. You did not explain > how you came to realize that the skel_probe() function is not being called - > I made an interesting discovery recently that may be relevant. > > In order to read the kernel debug messages, I have been using 'cat kmsg' in > the /proc directory. I found that the output was not giving me all the > expected messages. Sometimes it would tell me when the device was probed, > sometimes not. Even with two consecutive msg() calls in the same function, > sometimes the output would only display one of them. With the command > "tail /var/log/messages -f" I seem to get much more consistant results. > Obviously, now I rely on the second method. > > I am still fairly novice at kernel module development, and it would be nice if > anyone has an explantion. Should /proc/kmsg show all the kernel messages?
You should use the dmesg program to read kernel messages. > On Monday 18 October 2004 10:07 am, Mikolaj Zuberek wrote: > > Hi, > > > > I used the usb-skeleton.c as a starting point to develop usb host driver > > for USB memory stick. This may seem like a silly question, but why are you developing a USB driver for memory sticks when there's already a perfectly good usb-storage driver in the kernel? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
