On 11/22/2012 09:09 PM, Michal Nazarewicz wrote:
* Andrzej Pietrasiewicz | 2012-11-22 13:06:54 [+0100]:
During its lifetime, the mass storage can require creating
lunX directories for its luns. And again, with usbf_option
On Thu, Nov 22 2012, Sebastian Andrzej Siewior wrote:
You have first to detach the gadget because you can't update while it
is in progress connected / working. If you add an additional LUN then
there is no way to notify the host side about this.
I believe the point was that this happens during configuration. The way
I see it is that user writes number of luns it wants the gadget to
have into a configfs file at which point the function creates lun#
directories so that each lun can be configured separately.
That is okay then. On tcm you simply mkdir lun_directory.
I also show how to write an adapter module, which provides
the old sysfs-based interface to mass storage with module parameters,
but internally operates on configfs.
There is no sysfs interface, is there? We have only modprobe
interface.
f_mass_storage creates a device and thus a sysfs entry for each LUN.
This, among other things, allows setting up of the backing file if the
LUN is removable.
I see. But there is no way to notify the host that you removed the disk
or inserted it back, right?
Sebastian
--
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
