You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when running USB MSC with FAT file system disk on host side it is visible as "non label volume":
This form of volume presentation on host OS is especially confusing when there is MSC with multiple LUNs (like on the screenshot above).
It turns out that FAT FS implementation is supporting f_setlabel(...) function which could be used for volume label configuration. The question here is: how it should be handled from user app?
File System interface is limited to only those actions. So there are 2 options:
extend File System API to add something like .setlabel field,
insert f_setlabel(...) call inside one of already existing API functions (maybe fatfs_mount?).
Please give me a feedback what do you thinks about that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently when running USB MSC with FAT file system disk on host side it is visible as "non label volume":
This form of volume presentation on host OS is especially confusing when there is MSC with multiple LUNs (like on the screenshot above).
It turns out that FAT FS implementation is supporting
f_setlabel(...)
function which could be used for volume label configuration. The question here is: how it should be handled from user app?File System
interface is limited to only those actions. So there are 2 options:File System
API to add something like.setlabel
field,f_setlabel(...)
call inside one of already existing API functions (maybefatfs_mount
?).Please give me a feedback what do you thinks about that.
Beta Was this translation helpful? Give feedback.
All reactions