9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: [9front] [PATCH 0/5] USB audio 2.0
Date: Fri, 18 Nov 2022 19:27:34 -0800	[thread overview]
Message-ID: <cover.1668828454.git.mforney@mforney.org> (raw)

Looking for people with USB audio devices to test this series. I
have two devices (one 1.0 and one 2.0), and both seem to work, but
the more testing the better.

Note that since 2.0 devices use an IAD, nusbrc auto-detection doesn't
work for them; you'll need to either add your device IDs to nusbrc,
or start nusb/audio manually.

The patches are also available in the "audio" branch of
https://git.sr.ht/~mcf/plan9front if that's more convenient for
you.

Michael Forney (5):
  nusb: move audio-specific requests to nusb/audio
  nusb/audio: remove code for bi-directional endpoint
  nusb/audio: only consider data endpoints when setting up stream
  nusb/audio: enumerate streams through control interface
  nusb/audio: add support for USB audio 2.0

 sys/src/cmd/nusb/audio/audio.c | 470 ++++++++++++++++++++++++++-------
 sys/src/cmd/nusb/lib/usb.h     |  14 +-
 2 files changed, 386 insertions(+), 98 deletions(-)

-- 
2.37.3


             reply	other threads:[~2022-11-19  3:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  3:27 Michael Forney [this message]
2022-11-18  9:11 ` [9front] [PATCH 1/5] nusb: move audio-specific requests to nusb/audio Michael Forney
2022-11-18  9:11 ` [9front] [PATCH 2/5] nusb/audio: remove code for bi-directional endpoint Michael Forney
2022-11-18  9:11 ` [9front] [PATCH 3/5] nusb/audio: only consider data endpoints when setting up stream Michael Forney
2022-11-18  9:21 ` [9front] [PATCH 4/5] nusb/audio: enumerate streams through control interface Michael Forney
2022-11-18 20:35 ` [9front] [PATCH 5/5] nusb/audio: add support for USB audio 2.0 Michael Forney

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=cover.1668828454.git.mforney@mforney.org \
    --to=mforney@mforney.org \
    --cc=9front@9front.org \
    /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).