On Thu, 2 Jul 2009, Giacomo Lozito wrote: > >You don't actually need the new flag. Although it might be considered > >abuse, you can set the SINGLE_LUN flag for this device and then > >override the value in your initialization function. > > Yes, I had thought about that. And it certainly works as long as SINGLE_LUN is > checked (and max_lun is set to 0) -before- usb_stor_acquire_resources is > called. > But then I thought it might be better to have a flag that is made to obtain > that specific behaviour rather than to set the SINGLE_LUN flag with the above > speculation just cause it currently works. > My two cents, of course :) Yeah, abusing SINGLE_LUN this way probably isn't a good idea. > >Does this device work correctly under Windows? If so, how? > > It works correctly on Windows Vista. > The device is seen as a single usb component but it displays four separate > disks on "my computer", even when no card is inserted in (just like a CD > reader). The point of my question is: How does Windows know there are four LUNs? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
