From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933733AbcLIOnL (ORCPT ); Fri, 9 Dec 2016 09:43:11 -0500 Received: from resqmta-po-10v.sys.comcast.net ([96.114.154.169]:58852 "EHLO resqmta-po-10v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932594AbcLIOnJ (ORCPT ); Fri, 9 Dec 2016 09:43:09 -0500 Reply-To: shuah@kernel.org Subject: Re: Fwd: Antwort: Re: vUDC References: <67b23509-71f2-7e85-6b6e-807041661ec0@samsung.com> To: Krzysztof Opasiak , elen.niedermeyer@biotronik.com Cc: Shuah Khan , linux-usb@vger.kernel.org, kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org, shuahkh@osg.samsung.com, Shuah Khan From: Shuah Khan Message-ID: <16c02261-4f41-7e75-8b70-64534b4ed971@kernel.org> Date: Fri, 9 Dec 2016 07:43:06 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <67b23509-71f2-7e85-6b6e-807041661ec0@samsung.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfHChAeiNCnH+bgUfZsBTItpSSypIJfWrA8vwRwiWs1yscmvdXKGrZhZYmZTBGsInlj/uYYCtQJtBiI/9OEYmZZbwcumnpAS2yH91tovQwLZ3CjIRfr75 cFwjN4eEJTx9xBB27Gk+CmuyPmu9HY83tZMLBdxSPczDBF4y2jStokhG6K1sGSisr2vW0gfSRhYwW1TQOxyd4fhUOwuWepdGwGGh59y1PSKh/oniuVRlQqk9 7baF2+qVEHUylmHmG0M3AquhGABSCW3Xuku+7uKqJrY0Et7yNYJw045utSpDsNk7fmBvg4uuHug3mOoD8g7Z4R4dAO/XM1PnLzg47oG+4jfZhQTrZxQ1zXFp uCoWGgHv6DL5460g+2NMDJ8WBqR5K1By3CI5BpI4FYCiMqZ+IsY= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Krzysztof, On 12/09/2016 01:43 AM, Krzysztof Opasiak wrote: > FYI to the list for next generations;) > > > -------- Forwarded Message -------- > Subject: Antwort: Re: vUDC > Date: Fri, 9 Dec 2016 09:00:04 +0100 > From: Elen Niedermeyer > To: Krzysztof Opasiak > > > Hi, > > so your script solved my problem. I didn't know that I should start the > daemon with 'usbipd --device' after starting my emulation. I've tried it > with 'usbip -d' and then bind my device with 'usbip bind -b BUSID'. But > there wasn't listet a device by usbip with 'usbip list -l', so I didn't > know what I have to bind. Mit freundlichen Grüßen > Kind regards, > > i.A. Elen Niedermeyer > Duale Studentin Informatik > __________________________ > > BIOTRONIK SE & Co. KG > Woermannkehre 1 > 12359 Berlin, Germany > > Phone: +49 (0) 30 68905-2459 > Fax: +49 (0) 30 68905 2940 > Mail: elen.niedermeyer@biotronik.com > > -----Krzysztof Opasiak schrieb: ----- > An: Shuah Khan , Elen Niedermeyer > > Von: Krzysztof Opasiak > Datum: 08.12.2016 16:11 > Kopie: linux-usb@vger.kernel.org, kernelnewbies@nl.linux.org, LKML > , shuah@kernel.org > Betreff: Re: vUDC > > Hi, > > On 12/08/2016 03:33 PM, Shuah Khan wrote: >> Hi Elen, >> >> Adding k.opasiak@samsung.com >> >> On Thu, Dec 8, 2016 at 7:07 AM, Elen Niedermeyer >> wrote: >>> Dear Sir or Madam, >>> >>> I'm trying to run usbip-vudc since a few days. I want to access my emulated usb devices over usbip. >>> I use Ubuntu 16.04.01 and updated my kernel to version 4.8.0-30. I've installed linux-tools-4.8.0-30-generic which includes usbip. I enabled the modules usbip-host and usbip-vudc on the server. Futhermore I use configfs to emulate the usb devices. >>> So I could start the daemon and my emulation. But I can't detect my emulated usb device with usbip to bind it. >>> Could you help me to run usbip-vudc? Do I have to install an additional package? Do I miss a step? >>> >>> Mit freundlichen Grüßen >>> Kind regards, >> >> Could you please send your dmesg? Also could you run usbipd with >> --debug and usbip with --log option and send the syslog >> >> Krzysztof, >> > > You setup script should look like this: > > Server: > $ modprobe usbip-vudc > # Create your gadget, for example: > $ cd /sys/kernel/config/usb_gadget > $ mkdir g1 > $ mkdir g1/functions/acm.ser0 > $ mkdir g1/configs/c.1 > $ ln -s g1/functions/acm.ser0 g1/configs/c.1 > $ echo "0x1234" > g1/idVendor > $ echo "0x5678" > g1/idProduct > $ echo usbip-vudc.0 > UDC > $ usbipd --device > > Client: > $ modprobe usbip-vhci > $ usbip attach -r $SERVER_IP -d usbip-vudc.0 > > Please let me know if your setup script is similar and what exactly is I would be good to create server_sample.sh and client_sample.sh and add them to tools/usb/usbip - users can customize them. What do you think? Is this something you have time for? thanks, -- Shuah