From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: No sound on xps 17 9700 - need new kernel flags?
Date: Tue, 01 Jun 2021 00:22:39 +0200 [thread overview]
Message-ID: <20210531222239.MAYQWxehRvsepbD2jLEYCoi93XnNsX9FqOPEOD6mOT8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30508@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/30508#issuecomment-851702827
Comment:
We have `CONFIG_SND_SOC_RT1308_SDW=m` in our configs already, but not `CONFIG_SND_SOC_RT1308` by itself.
`CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH` needs to be enabled and I think it will "unlock" `CONFIG_SND_SOC_RT1308`.
`CONFIG_SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES` is just a user experience thing, and I don't think we should enable it.
```
config SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES
bool "Use more user friendly long card names"
help
Some drivers report the I/O configuration to userspace through the
soundcard's long card name in the control user space AP. An unfortunate
side effect is that this long name may also be used by the GUI,
confusing users with information they don't need.
This option prevents the long name from being modified, and the I/O
configuration will be provided through a different component interface.
Select Y if userspace like UCM (Use Case Manager) uses the component
interface.
If unsure select N.
```
Re. how to build a kernel, just edit the config in `srcpkgs/linux5.12/files/x86_64-dotconfig`, `./xbps-src pkg -f linux5.12` and `xi -f linux5.12`.
next prev parent reply other threads:[~2021-05-31 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 8:29 [ISSUE] " gronka
2021-05-31 17:40 ` gronka
2021-05-31 22:22 ` ericonr [this message]
2021-05-31 23:08 ` gronka
2021-06-01 1:13 ` ericonr
2021-08-05 21:13 ` gronka
2021-08-05 21:14 ` gronka
2021-08-10 11:28 ` [ISSUE] [CLOSED] " leahneukirchen
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=20210531222239.MAYQWxehRvsepbD2jLEYCoi93XnNsX9FqOPEOD6mOT8@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).