All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Lenovo Legion ALC287/ALC3306 issue
Date: Mon, 21 Jun 2021 00:43:57 +0200 (CEST)	[thread overview]
Message-ID: <20210620224357.5F630F80268@alsa1.perex.cz> (raw)
In-Reply-To: <1624229033089593887-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #160 was opened from camberkenpas:

Hello,

I was able to do a little digging into this issue by running a Windows 10 virtual machine and passing the sound card device to the virtual machine I was able to get audio to play through the laptop's virtual machine using the virtual machine. More importantly, I was able to capture traces that might help us determine what this sound card needs.

I've attached traces at the ticket for this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=208555

Perhaps this is enough to deduce at least some of what verbs the codec wants in order to work.

Is this the right place to share this? Or is the kernel bug tracker the only appropriate place for this?

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/160
Repository URL: https://github.com/alsa-project/alsa-lib

           reply	other threads:[~2021-06-20 22:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1624229033089593887-webhooks-bot@alsa-project.org>]

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=20210620224357.5F630F80268@alsa1.perex.cz \
    --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 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.