From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Accident
Date: Mon, 16 Mar 2026 21:29:39 +0100 (CET) [thread overview]
Message-ID: <189d6c5d95278100-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <189d6c5d951dea00-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #723 was edited from P-v-D:
`cat /proc/asound/card0/stream0
Roland BRIDGE CAST X-I V2 at usb-0000:09:00.1-2, high speed : USB Audio
Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 392
Momentary freq = 48000 Hz (0x6.0000)
Interface 1
Altset 1
Format: S32_LE
Channels: 14
Endpoint: 0x0d (13 OUT) (ASYNC)
Rates: 48000
Data packet interval: 125 us
Bits: 24
Channel map: FL FR FC LFE RL RR FLC FRC RC SL SR TC -- --
Sync Endpoint: 0x8e (14 IN)
Sync EP Interface: 2
Sync EP Altset: 1
Implicit Feedback Mode: Yes
Capture:
Status: Stop
Interface 2
Altset 1
`
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/723
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2026-03-16 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <189d6c5d951dea00-webhooks-bot@alsa-project.org>
2026-03-16 20:29 ` GitHub issues - edited [this message]
[not found] <189d6c63342cd800-webhooks-bot@alsa-project.org>
2026-03-16 20:30 ` Accident GitHub issues - edited
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=189d6c5d95278100-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.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