Hello Alern San,

Thank you so much for your reply, I will make sure that I forward these 
questions to linux-usb mailing list (CC'ed).

I successfully cross complied usb.c on my Ubuntu machine, also I changed my 
controller to the SabreSD specific (ci_hdrc_imx),  after executing it on 
target, it gave me following output : 
----------------------------------------------------------------------------------------------------------------------------------------------
gadgetfs: bound to ci_hdrc_imx driver                     
/dev/gadget/ci_hdrc_imx ep0 configured                                  
serial="xce5r4f5wv60w958rm8yqv71ur7bk6nwmvoy87o7q0gimixl55lck514kbtj0bv"
----------------------------------------------------------------------------------------------------------------------------------------------

Thank you for your guidance, I am exploring it more for image transfer. In case 
of any further question I will post it to you with linux-usb CC'ed.

Thanks and Regards
Ashwin Deshpande


________________________________________
From: Alan Stern [[email protected]]
Sent: 04 February 2015 23:16
To: Ashwin A Deshpande
Cc: USB list
Subject: Re: USB Gadgetfs

On -1 xxx -1 [email protected] wrote:

> Hello Alern San,
>
> This is with reference to 
> http://libusb.6.n5.nabble.com/How-to-send-receive-data-using-gadgetfs-bulk-endpoint-td5076584.html

Questions like this should be sent to the linux-usb mailing list
(CC'ed).

> I am trying to configure freescale's iMX6 SabreSD board as device and
> UBUNTU Desktop as a host and transfer images over USB using gadgetfs,
> i have googled so many links but I am not clear about the exact
> procedure to follow.
>
> All examples states, run usb.c, but how to make an executable for my
> target board (iMX6 SabreSD).

Compile usb.c.  Or cross-compile it on a different computer, if you
don't have a compiler that runs on the SabreSD.

> Also the controllers stated in autoconfig() functions doesn't match
> with the one used in SabreSD.

I don't think that matters very much, so long as your controller
provides the necessary endpoints.

> If i follow the procedure
> 1) mkdir /dev/gadget
> 2) modprobe gadgetfs
> 3) mount -t gadgetfs none /dev/gadget
>
> I get an error "nop ci_hdrc.0: failed to start (null): -120"

Somebody who is more familiar with the ci_hdrc driver will have to
answer this.

> If you can guide with step by step procedure, I would be thankful
>
> Thanks and Regards
> Ashwin Deshpande

Alan Stern


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Information contained and transmitted by this e-mail is confidential and 
proprietary to IGATE and its affiliates and is intended for use only by the 
recipient. If you are not the intended recipient, you are hereby notified that 
any dissemination, distribution, copying or use of this e-mail is strictly 
prohibited and you are requested to delete this e-mail immediately and notify 
the originator or [email protected] <mailto:[email protected]>. IGATE does 
not enter into any agreement with any party by e-mail. Any views expressed by 
an individual do not necessarily reflect the view of IGATE. IGATE is not 
responsible for the consequences of any actions taken on the basis of 
information provided, through this email. The contents of an attachment to this 
e-mail may contain software viruses, which could damage your own computer 
system. While IGATE has taken every reasonable precaution to minimise this 
risk, we cannot accept liability for any damage which you sustain as a result 
of software viruses. You should carry out your own virus checks before opening 
an attachment. To know more about IGATE please visit www.igate.com 
<http://www.igate.com>.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to