Would it be acceptable that the automount handler is called from usbhost_storage.c, from a modularity point of view? Because that way it would be only a notification towards the work queue, using a mechanism that is already in place. I don't like the idea to have another kthread that does only wait for a notification/event and then schedules itself the automount work on the queue.
Johannes > -----Original Message----- > From: Gregory Nutt [mailto:spudan...@gmail.com] > > > But: I haven't yet found a way to determine if I enumerated really a mass > storage class device. So with only activating mass storage it seems rather > clean, but if I have multiple class drivers active, it gets complicated. > > Can you give a hint how to retrieve the type of driver bound to the > currently enumerated device? > That precise information is not available unless you add a notifier. > Bu you should be able to just use nx_stat() to see of the block driver > was created at /dev/sd* >
