linux-kernel - Re: vUDC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ac2054a0-aa0c-a348-f7b4-79e16fb5e86e@kernel.org>
Date:   Thu, 8 Dec 2016 08:47:27 -0700
From:   Shuah Khan <shuah@...nel.org>
To:     Krzysztof Opasiak <k.opasiak@...sung.com>,
        Elen Niedermeyer <elen.niedermeyer@...tronik.com>
Cc:     Shuah Khan <shuahkhan@...il.com>, linux-usb@...r.kernel.org,
        kernelnewbies@...linux.org, LKML <linux-kernel@...r.kernel.org>,
        Shuah Khan <shuahkh@....samsung.com>,
        Shuah Khan <shuah@...nel.org>
Subject: Re: vUDC

On 12/08/2016 08:07 AM, Krzysztof Opasiak wrote:
> Hi,
> 
> On 12/08/2016 03:33 PM, Shuah Khan wrote:
>> Hi Elen,
>>
>> Adding k.opasiak@...sung.com
>>
>> On Thu, Dec 8, 2016 at 7:07 AM, Elen Niedermeyer
>> <elen.niedermeyer@...tronik.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
> not working for you.
> 
>> Any ideas. Maybe it is time the documentation is updated with vudc details.
>>
> 
> Yes I think it's a good idea. I'll try to do this when I have some spare
> time.
> 
> Best regards,
> 

Thanks Krzysztof. When you get around to it, let's just add it under
Documentation. You can create a new file usbip.txt (guess at some
point we have to make .rst)

thanks,
-- Shuah