linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Krzysztof Opasiak <k.opasiak@samsung.com>,
	elen.niedermeyer@biotronik.com
Cc: Shuah Khan <shuahkhan@gmail.com>,
	linux-usb@vger.kernel.org, kernelnewbies@nl.linux.org,
	linux-kernel@vger.kernel.org, shuahkh@osg.samsung.com,
	Shuah Khan <shuah@kernel.org>
Subject: Re: Fwd: Antwort: Re: vUDC
Date: Fri, 9 Dec 2016 07:43:06 -0700	[thread overview]
Message-ID: <16c02261-4f41-7e75-8b70-64534b4ed971@kernel.org> (raw)
In-Reply-To: <67b23509-71f2-7e85-6b6e-807041661ec0@samsung.com>

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 <elen.niedermeyer@biotronik.com>
> To: Krzysztof Opasiak <k.opasiak@samsung.com>
> 
> 
> 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 <k.opasiak@samsung.com> schrieb: -----
> An: Shuah Khan <shuahkhan@gmail.com>, Elen Niedermeyer
> <elen.niedermeyer@biotronik.com>
> Von: Krzysztof Opasiak <k.opasiak@samsung.com>
> Datum: 08.12.2016 16:11
> Kopie: linux-usb@vger.kernel.org, kernelnewbies@nl.linux.org, LKML
> <linux-kernel@vger.kernel.org>, 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
>> <elen.niedermeyer@biotronik.com> 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

  reply	other threads:[~2016-12-09 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF3824F794.22BECE87-ONC1258084.002BBF3A-C1258084.002BF397@LocalDomain>
2016-12-09  8:43 ` Fwd: Antwort: Re: vUDC Krzysztof Opasiak
2016-12-09 14:43   ` Shuah Khan [this message]
2016-12-09 17:12     ` Krzysztof Opasiak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16c02261-4f41-7e75-8b70-64534b4ed971@kernel.org \
    --to=shuah@kernel.org \
    --cc=elen.niedermeyer@biotronik.com \
    --cc=k.opasiak@samsung.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=shuahkhan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).