[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87cymedlrt.wl-tiwai@suse.de>
Date: Mon, 12 Aug 2024 13:27:02 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Antheas Kapenekakis <lkml@...heas.dev>
Cc: Jonathan LoBue <jlobue10@...il.com>,
perex@...ex.cz,
tiwai@...e.com,
shenghao-ding@...com,
kailang@...ltek.com,
alsa-devel@...a-project.org,
linux-sound@...r.kernel.org,
linux-kernel@...r.kernel.org,
derekjohn.clark@...il.com,
luke@...nes.dev,
benato.denis96@...il.com,
Kyle Gospodnetich <me@...egospodneti.ch>,
Jan Drogehoff <sentrycraft123@...il.com>,
Richard Alvarez <alvarez.richard@...il.com>,
Miles Montierth <cyber_dopamine@...heblackmedia.com>,
"Chen, Robin" <robinchen@...com>
Subject: Re: [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio
On Mon, 12 Aug 2024 09:45:59 +0200,
Antheas Kapenekakis wrote:
>
> Hi,
> I have spoken with Shenghao and Robin Chen (who I CC) from Texas Instruments.
>
> There is no such thing as TAS2XXX1EB3. For Ally X, there are two firmware files:
> TAS2XXX1EB30 and TAS2XXX1EB31. Both are licensed with GPL
> according to Shenghao.
>
> Since the linux driver has no concept of the 0 and 1 suffix, I propose
> we symlink the
> 0 one to TAS2XXX1EB3. If required, the driver can be augmented in the future
> to either choose the 0 or 1 file.
Yes, symlinking in linux-firmware tree makes sense.
It's just a matter of a line in WHENCE file, after all.
Takashi
Powered by blists - more mailing lists