> On Mon, 26 Nov 2012, Sebastian Andrzej Siewior wrote: >> Step two is a folder where we setup individual configuration of a function. >> >> /functions/ttyS0 >> /functions/ttyS1 >> /functions/storage >> >> each one of the function folder has the file called "name". So for the >> folder ttyS0 the file name contains "acm" because we use the ACM >> function. The same is true for ttyS1 and for storage we write >> "mass_storage" if that is what function will be called. On Mon, Nov 26 2012, Alan Stern wrote: > Is there really any significant configuration to be done at this level? > I would expect functions to be written so that different settings can > be applied to different instances. > > For example, if a config had two mass-storage interfaces, they should > be configurable separately. There should be very little, or nothing, > that would apply across all the instances. In Sebastian's example, those are the instances which are attached to gadgets. A “pure” function has no representation. -- Best regards, _ _ .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michał “mina86” Nazarewicz (o o) ooo +----<email/xmpp: mpn@xxxxxxxxxx>--------------ooO--(_)--Ooo--
Attachment:
pgpV6tQWnTzSB.pgp
Description: PGP signature
