From: Felipe Balbi <balbi@kernel.org>
To: Sid Spry <sid@aeam.us>, Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: Documentation for Raw USB ConfigFS
Date: Wed, 13 May 2020 10:36:05 +0300 [thread overview]
Message-ID: <87h7wkp9qy.fsf@kernel.org> (raw)
In-Reply-To: <8ee3914e-7876-46aa-bade-7cf14df7efdc@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Hi,
"Sid Spry" <sid@aeam.us> writes:
> Hi Peter, thanks for pointing me towards the ffs-test. Unfortunately after
> some exploration in that area I still don't see how I would add a preexisting
> function to the configuration to be handled by the kernel.
>
> I do see something in an AIO test in the host code where libusb is used to
> bind a kernel driver to an endpoint. Is that something that will be necessary?
> Device side, I'm still unsure how I tell the function to handle ECM/ethernet
> on a collection of endpoints.
>
> I understand how USB works fairly well, especially on microcontrollers, but am
> a little lost still in understanding the Linux machinery for USB.
please, stop with your top-posting and break your lines at 80-columns. I
have re-wrapped your lines so you see how they should look.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-05-13 7:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 17:08 Documentation for Raw USB ConfigFS Sid Spry
2020-05-06 9:17 ` Peter Chen
2020-05-12 15:14 ` Sid Spry
2020-05-13 7:36 ` Felipe Balbi [this message]
2020-05-13 10:05 ` Peter Chen
2020-05-14 16:32 ` Sid Spry
2020-05-15 1:05 ` Peter Chen
2020-05-16 5:57 ` Sid Spry
2020-05-18 5:48 ` Peter Chen
2020-05-18 22:14 ` Sid Spry
2020-05-18 23:58 ` Peter Chen
2020-05-19 19:12 ` Sid Spry
2020-05-19 19:40 ` Sid Spry
2020-05-19 19:51 ` Krzysztof Opasiak
2020-05-20 5:27 ` Sid Spry
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=87h7wkp9qy.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=sid@aeam.us \
/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.