All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Gunnarsson <gunnarsson.lars@gmail.com>
To: Valentina Manea <valentina.manea.m@gmail.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-usb@vger.kernel.org
Subject: [PATCH v6 0/5] tools/usbip: Patch set summary
Date: Tue, 30 Nov 2021 23:22:54 +0100	[thread overview]
Message-ID: <20211130222254.GA16447@dell-precision-T3610> (raw)

To forward a remote usb device over usbip the following steps is required:

1. Execute "usbip bind" on remote end.
2. Execute "usbip attach" on local end.

These steps must be perfomed in above order and after usb device is plugged in.
If the usb device is unplugged on the remote end the steps above needs to be
performed again to establish the connection. This patch set implements a feature
to persistently forward devices on a given bus. When using flag "-p|--persistent"
on remot end, the USB device becomes exported when plugged in. When using flag
"-p|--persistent" on local end, the USB device becomes imported when available
on remote end. Thus it is only required to run the usbip command once on each
end, in any order, to persistently forward usb devices on a given bus.

This is sent in five separate patches:
  tools/usbip: update protocol documentation
  tools/usbip: update manual pages
  tools/usbip: add usb event monitor into libusbip
  tools/usbip: export USB devices on a given bus persistently
  tools/usbip: import USB devices on a given bus persistently

             reply	other threads:[~2021-11-30 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 22:22 Lars Gunnarsson [this message]
2021-12-03 11:17 ` [PATCH v6 0/5] tools/usbip: Patch set summary Greg KH
2021-12-06 20:02 ` Shuah Khan
2021-12-09 21:11   ` Lars Gunnarsson
2021-12-14 22:22     ` Shuah Khan
2021-12-16 21:01       ` Lars Gunnarsson
2021-12-23 19:22         ` Shuah Khan

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=20211130222254.GA16447@dell-precision-T3610 \
    --to=gunnarsson.lars@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=valentina.manea.m@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.