From: Diederik de Haas <didi.debian@cknow.org>
To: linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Sound issues with the 5.10.x kernel (alsa)
Date: Tue, 16 Feb 2021 01:12:12 +0100 [thread overview]
Message-ID: <11208610.7f3IsiomVT@bagend> (raw)
In-Reply-To: <b0be09a0-5ec3-b716-4b77-1dde43719273@i2se.com>
[-- Attachment #1.1: Type: text/plain, Size: 1215 bytes --]
On maandag 8 februari 2021 13:22:56 CET Stefan Wahren wrote:
> Currently i cannot see any of the fixes by Phil
> Elwell in linux-stable. Maybe they won't apply and needs to be backport
> manually.
>
> Just for reference here are the revelant patches:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/d
> rivers/staging/vc04_services?h=next-20210205&id=96ae327678eceabf455b11a88ba1
> 4ad540d4b046
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/d
> rivers/staging/vc04_services?h=next-20210205&id=88753cc19f087abe0d39644b844e
> 67a59cfb5a3d
>
> Could you please try?
I've now successfully build and booted a 5.10.16 kernel 'pristine' and with
the above mentioned patches.
In the 'pristine' variant, I had the same bad/horrible quality as I
experienced with Debian's 5.10 kernels.
The 'patched' variant seems to be a tad better, but didn't completely solve
the audio problem. There's still some noise intermixed with the music and
other artifacts, but I'm inclined to think it's not as horrible as before.
I'll do some more hearing tests tomorrow when I'm fresh again, but figured I'd
share these preliminary results already.
Cheers,
Diederik
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2021-02-16 0:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3165951.nLcn7dHqa8@bagend>
2021-02-08 12:22 ` Sound issues with the 5.10.x kernel (alsa) Stefan Wahren
2021-02-08 12:50 ` Diederik de Haas
2021-02-16 0:12 ` Diederik de Haas [this message]
2021-02-16 14:38 ` Diederik de Haas
2021-03-28 0:48 ` Ryutaroh Matsumoto
2021-03-28 5:58 ` Ryutaroh Matsumoto
2021-03-28 9:29 ` Stefan Wahren
2021-03-28 23:13 ` Ryutaroh Matsumoto
2021-03-28 23:17 ` Ryutaroh Matsumoto
[not found] ` <20210208.230026.1706784668119437570.ryutaroh@ict.e.titech.ac.jp>
2021-02-08 14:31 ` Diederik de Haas
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=11208610.7f3IsiomVT@bagend \
--to=didi.debian@cknow.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
/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).