On Wed, Aug 31, 2005 at 03:00:13PM +0300, Jouni Ryn? wrote: > I'm replying to myself, just that someone else could propably find (by > googling) the issue interesting > > Anyway, I solved my problem by using a new char device and class for my > USB device. > > alloc_chrdev_region(&x2s_dev, 0, X2S_NR_OF_DEVICES*X2S_MINORS, > "x2s_usb"); > > x2s_class = class_simple_create(THIS_MODULE, "x2s_usb"); > > And then I was able to do whatever I wanted with the char device entries > and minors. Now I have only firmware loading device appearing upon > plug-in. The block and iso streams become available, when the firmware > is succesfully loaded. > > How reasonable it is to create new classes, I don't know. But it works.
If you have your own major number, it's fine to create a new class. thanks, greg k-h ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
