From: Takashi Iwai <tiwai@suse.de>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: Jonathan LoBue <jlobue10@gmail.com>,
perex@perex.cz, tiwai@suse.com, shenghao-ding@ti.com,
kailang@realtek.com, alsa-devel@alsa-project.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
derekjohn.clark@gmail.com, luke@ljones.dev,
benato.denis96@gmail.com,
Kyle Gospodnetich <me@kylegospodneti.ch>,
Jan Drogehoff <sentrycraft123@gmail.com>,
Richard Alvarez <alvarez.richard@gmail.com>,
Miles Montierth <cyber_dopamine@intheblackmedia.com>,
"Chen, Robin" <robinchen@ti.com>
Subject: Re: [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio
Date: Mon, 12 Aug 2024 13:27:02 +0200 [thread overview]
Message-ID: <87cymedlrt.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGwozwF7aR5UypRTe7tNFR+xOfQ=rhqkzYUgBcYH4_LvO9_zXQ@mail.gmail.com>
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
next prev parent reply other threads:[~2024-08-12 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 4:53 [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio Jonathan LoBue
2024-08-12 7:26 ` Takashi Iwai
2024-08-12 7:45 ` Antheas Kapenekakis
2024-08-12 11:27 ` Takashi Iwai [this message]
2024-08-15 12:58 ` Antheas Kapenekakis
2024-10-11 5:20 ` Philip Müller
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=87cymedlrt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=alvarez.richard@gmail.com \
--cc=benato.denis96@gmail.com \
--cc=cyber_dopamine@intheblackmedia.com \
--cc=derekjohn.clark@gmail.com \
--cc=jlobue10@gmail.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
--cc=me@kylegospodneti.ch \
--cc=perex@perex.cz \
--cc=robinchen@ti.com \
--cc=sentrycraft123@gmail.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.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