On Tue, 8 Jun 2004, Dan Scholnik wrote: > On Mon, 2004-06-07 at 17:28, Alan Stern wrote: > > Dan: > > > > By the way, I just noticed that the Casio QV unusual_devs.h entry has > > US_FL_FIX_INQUIRY. Do you know why it's there, or if it's really > > needed? Can you post a usb-storage debugging log showing what happens > > when you remove that flag? > > > > (I have a long-running background project to remove as many of those > > FIX_INQUIRY flags as possible. A lot of them are unnecessary now that > > other parts of usb-storage and the SCSI disk driver have been fixed up.) > > > > Alan Stern > > I have no idea why it was there beyond the comment above the entry; > don't confuse my ability to recognize when my camera stopped working and > to use diff to track down the culprit with any actual knowledge about > USB... :) > > Anyway, I replaced US_FL_FIX_INQUIRY with 0, and my camera still seems > to work fine. I'm attaching the relevant output from /var/log/messages > and dmesg; there are 3 dumps from dmesg taken (in sequence) after > plugging the camera in, after mounting it, and then after unmounting > it. Still, I think some log info was probably lost, there's a lot of > it. Hope it helps. > > Dan Scholnik
Yes, the logs look perfect. On the other hand, the INQUIRY returns almost no useful data: no vendor name, model name, or revision level. Maybe that's a good reason for keeping the flag. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
