linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ding, Shenghao" <shenghao-ding@ti.com>
To: Gergo Koteles <soyer@irl.hu>
Cc: "Lu, Kevin" <kevin-lu@ti.com>, "Xu, Baojun" <baojun.xu@ti.com>,
	"13916275206@139.com" <13916275206@139.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Gupta, Peeyush" <peeyush@ti.com>,
	"Navada Kanyana, Mukund" <navada@ti.com>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH v1] ASoC: tas2781: Add dsp firmware for different laptops
Date: Thu, 28 Dec 2023 14:49:29 +0000	[thread overview]
Message-ID: <23e85f35969447ab9161068f2c159845@ti.com> (raw)
In-Reply-To: <95023a6158e1359c18797d7ed10a6914cf781f84.camel@irl.hu>



> -----Original Message-----
> From: Gergo Koteles <soyer@irl.hu>
> Sent: Thursday, December 28, 2023 9:55 PM
> To: Ding, Shenghao <shenghao-ding@ti.com>; linux-firmware@kernel.org
> Cc: Lu, Kevin <kevin-lu@ti.com>; Xu, Baojun <baojun.xu@ti.com>;
> 13916275206@139.com; linux-sound@vger.kernel.org; linux-
> kernel@vger.kernel.org; Gupta, Peeyush <peeyush@ti.com>; Navada
> Kanyana, Mukund <navada@ti.com>
> Subject: Re: [EXTERNAL] Re: [PATCH v1] ASoC: tas2781: Add dsp firmware for
> different laptops
> 
> Hi Shenghao,
> 
> On Thu, 2023-12-28 at 07:29 +0000, Ding, Shenghao wrote:
> > > On Sat, 2023-12-23 at 22:12 +0800, Shenghao Ding wrote:
> > > >
> > > > +Licence: Allegedly GPLv2+, but no source visible. Marked:
> > > > +	 Copyright (C) 2023 Texas Instruments
> > > > +
> > > > +Found in hex form in kernel source.
> > >
> > > Is this true? Isn't this a new driver?
> > Maybe following expression will be more clear Firmware will be found
> > in hex form in the system.
> 
> And what about the Licence?
> 
> I would like to add TAS2XXX3870.bin that I found in my computer's windows
> sound driver as Source/ThirdParty/TI/TAS2563Firmware.bin .
> 
> Could you please add it, or will TI give permission to redistribute these files?
> 
> The windows driver (innoextract compatible):
> https://download.lenovo.com/consumer/mobiles/h5yd037fbfyy7kd0.exe
> The RCA file I created:
> https://github.com/soyersoyer/tas2563rca/raw/main/INT8866RCA2.bin
> 
OK, I'll add in one or two days.
> 
> > >
> > > > \ No newline at end of file
> > > > diff --git a/ti/tas2781/TAS2XXX387D.bin
> > > > b/ti/tas2781/TAS2XXX387D.bin new file mode 100644 index
> > > >
> 
> Regards,
> Gergo


  reply	other threads:[~2023-12-28 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 14:12 [PATCH v1] ASoC: tas2781: Add dsp firmware for different laptops Shenghao Ding
2023-12-26 19:43 ` Josh Boyer
2023-12-27 11:40 ` Gergo Koteles
2023-12-28  7:29   ` [EXTERNAL] " Ding, Shenghao
2023-12-28 13:54     ` Gergo Koteles
2023-12-28 14:49       ` Ding, Shenghao [this message]
2024-03-09  5:33         ` Stuart Hayhurst

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=23e85f35969447ab9161068f2c159845@ti.com \
    --to=shenghao-ding@ti.com \
    --cc=13916275206@139.com \
    --cc=baojun.xu@ti.com \
    --cc=kevin-lu@ti.com \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=navada@ti.com \
    --cc=peeyush@ti.com \
    --cc=soyer@irl.hu \
    /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).