Hi, On Mon, Mar 18, 2013 at 10:23:32AM +0100, Andrzej Pietrasiewicz wrote: > > The prerequisite for providing the configfs interface for USB gadgets and > > all their users is converting them to the new function interface from > > Sebastian. > > > > This patch series serves the purpose stated above for mass storage, usb > > Ethernet, FunctionFS and serial. > > <snip> > > @Felipe, @Sebastian: Converting the above mentioned functions to the new > interface has already been a considerable effort, so could you please share > your opinion? > > I understand that Sebastian might not have enough time to do > this step of conversion to configfs himself, but with converting the > functions to the new function interface I followed his example > from e.g. acm. > > Additional questions: > > 1. Is converting the functions to the new function interface the > right way to go? (given the discussions so far I believe it is, > but kindly ask for confirmation or pointing at what to improve) > > 2. What is the preferred way of finally arriving at a configfs-based > gadget: breadth-first approach (convert all functions to the new > function interface, then move to configfs) or depth-first approach > (convert a function and then move it to configfs, then do the same > with some next function and so on) I think it's best to convert them one at a time, so that we can focus on a single function and make sure there are no regressions before working on the following one. What concerns me the most, however, is how do we keep the traditional modprobe g_mass_storage functionality once we move to configfs based approach ? We need to keep that around at least for a few years. Any suggestions are highly appreciated. -- balbi
Attachment:
signature.asc
Description: Digital signature
