From: Matt Porter <mporter@linaro.org>
To: Linux USB List <linux-usb@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stanislaw Wadas <s.wadas@samsung.com>,
Krzysztof Opasiak <k.opasiak@samsung.com>
Subject: libusbg 0.1.0 (formerly libgadget)
Date: Tue, 21 Jan 2014 09:24:37 -0500 [thread overview]
Message-ID: <20140121142437.GH31176@beef> (raw)
libusbg 0.1.0 is released. libusbg is a library that provides a C API to
the kernel USB gadget configfs API. It simplifies creation and
management of USB gadget devices from C applications.
Get it at:
git://github.com/libusbg/libusbg.git
API docs at:
http://libusbg.github.com/group__libusbg.html
http://libusbg.github.com/examples.html
Changes since libgadget 0.0.1:
- libusbg now has a new name to avoid conflicts
with an existing libgadget libary
- use the standard /sys/kernel/config mount path
in examples
- a new project home on github
Going forward we have a couple contributors with clean up and bug
fixes that will be rolled into libusbg once comments are addressed.
Support for FunctionFS (merged for 3.14) will also be added.
-Matt
reply other threads:[~2014-01-21 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140121142437.GH31176@beef \
--to=mporter@linaro.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.wadas@samsung.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