On Thu, 18 Apr 2013, Andrzej Pietrasiewicz wrote:
> On Wednesday, April 17, 2013 6:46 PM Alan Stern wrote:
> > On Wed, 17 Apr 2013, Andrzej Pietrasiewicz wrote:
> >
> > > The procedure of setting a gadget up with configfs is like this:
> > >
> > > 1) create the gadget directory
> > > 2) create fu
On Wednesday, April 17, 2013 6:46 PM Alan Stern wrote:
> On Wed, 17 Apr 2013, Andrzej Pietrasiewicz wrote:
>
> > The procedure of setting a gadget up with configfs is like this:
> >
> > 1) create the gadget directory
> > 2) create functions directories corresponding to functions to be used
> > by
On Wed, 17 Apr 2013, Andrzej Pietrasiewicz wrote:
> The procedure of setting a gadget up with configfs is like this:
>
> 1) create the gadget directory
> 2) create functions directories corresponding to functions to be used
> by the gadget
> 3) create configurations directories
...
> 4) create
On Wed, 17 Apr 2013, Andrzej Pietrasiewicz wrote:
> The procedure of setting a gadget up with configfs is like this:
>
> 1) create the gadget directory
> 2) create functions directories corresponding to functions to be used
> by the gadget
> 3) create configurations directories
>
> Anytime befor
On Friday, April 12, 2013 7:58 PM Alan Stern wrote:
> On Fri, 12 Apr 2013, Andrzej Pietrasiewicz wrote:
>
> > > > registered with register_netdev. But in order to register it, its
> > > > parent device must be known and it becomes known only later during
> > > > gadget's bind.
> > >
> > > Why must
On Fri, 12 Apr 2013, Andrzej Pietrasiewicz wrote:
> > > registered with register_netdev. But in order to register it, its
> > > parent device must be known and it becomes known only later during
> > > gadget's bind.
> >
> > Why must this happen before the gadget driver is bound? What can't it
>
On Thursday, April 11, 2013 5:00 PM Alan Stern wrote:
> On Thu, 11 Apr 2013, Andrzej Pietrasiewicz wrote:
>
> > This adds a new sysfs root device to serve as a replacement for
> > devices which are available only when a gadget is being bound.
> >
> > It is motivated by adding configfs support to U
On Thu, 11 Apr 2013, Andrzej Pietrasiewicz wrote:
> This adds a new sysfs root device to serve as a replacement for
> devices which are available only when a gadget is being bound.
>
> It is motivated by adding configfs support to USB Ethernet functions.
> When configfs is there, we would like to
This adds a new sysfs root device to serve as a replacement for
devices which are available only when a gadget is being bound.
It is motivated by adding configfs support to USB Ethernet functions.
When configfs is there, we would like to be able to mkdir some function
directory, e.g.:
$ mkdir fun
