On Mon, Oct 20, 2014 at 01:41:37PM +0200, Krzysztof Opasiak wrote: > Driver which provides implementation of some USB functions > registers its usb_function_driver structure in framework. > Function drivers are identifed using registered name. > > When gadget is composed user must know what names has been
"user *must" know", why ? > registered. If function is compiled as a module this > information can be found in modules.alias file. But if > function is compiled-in, there is no way to discover what > functions are available in currently running kernel. > > Such situation is nothing new for linux kernel. > Similar situation is with file systems. While mounting user > can provide an fs type using -t option in mount. Those type > names are registered by drivers. To make those names > discoverable there is a proc fs attribute filesystems which > exports the fils of currently registered file systems. > > This patch adds proc fs attribute which exports the list > of currently registered function drivers. This allows user > to discover list of both compiled-in functions and > from loaded kernel modules. ugh, new procfs files. Thanks, but no thanks. Also, I thought Sebastian had explained to you that Target framework does not provide any list of any sorts. -- balbi
signature.asc
Description: Digital signature
