public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: USB-Audio: Add support for the SSL 2 MK II
Date: Tue,  6 Jan 2026 19:23:04 +0100 (CET)	[thread overview]
Message-ID: <18883768f532d700-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/681@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #681 was opened from MTRNord:

This adds support for https://solidstatelogic.com/products/ssl-2-mkii and the https://solidstatelogic.com/products/ssl-2-plus-mkii and solves #555 

The MK II shows up the same way as the SSL2, but as a different USB Device.

I only own the SSL2 MK2, but not the SSL2+ MK2. So I can only verify it for the SSL2 MK2. However, I am fairly certain that the + version likely is also behaving identically. There are no visible spec changes between the v1 and MK2 of these devices, from all I was able to tell based on the internet. So, likely only the USB ID changed (at least for the things alsa-ucm is concerened about)

Request URL   : https://github.com/alsa-project/alsa-ucm-conf/pull/681
Patch URL     : https://github.com/alsa-project/alsa-ucm-conf/pull/681.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

       reply	other threads:[~2026-01-06 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alsa-project/alsa-ucm-conf/pr/681@alsa-project.org>
2026-01-06 18:23 ` GitHub pull_request - opened [this message]
2026-01-06 18:23 ` USB-Audio: Add support for the SSL 2 MK II and SSL2+ MK II GitHub pull_request - 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=18883768f532d700-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