linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"David Heidelberg" <david@ixit.cz>,
	"Peter Geis" <pgwipeout@gmail.com>,
	"Stephen Warren" <swarren@wwwdotorg.org>,
	"Nicolas Chauvet" <kwizart@gmail.com>,
	"Pedro Ângelo" <pangelo@void.io>,
	"Matt Merhar" <mattmerhar@protonmail.com>,
	linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500
Date: Tue, 7 Apr 2020 19:38:00 +0300	[thread overview]
Message-ID: <70ad6fd6-9603-a114-2d0f-608110b68c0b@gmail.com> (raw)
In-Reply-To: <20200407100829.GB1720957@ulmo>

07.04.2020 13:08, Thierry Reding пишет:
> On Mon, Apr 06, 2020 at 10:41:10PM +0300, Dmitry Osipenko wrote:
>> Enable several drivers for hardware that is found on Nexus 7 and Acer A500
>> tablet devices. Please note that some drivers may require firmware files
>> extracted from original Android image.
>>
>> Link: https://github.com/digetx/linux-firmware
> 
> What's the license for these files?

It's either GPL (like touchscreen config) or something else
redistributeable.

> Can they be made available through the official linux-firmware repository?

Yes, but I don't know yet for sure whether it's really needed for all
firmware files.

For example, the T30 Broadcom WiFi doesn't work using stock
linux-firmware, it's on my to-do list to try to figure out why.

While Bluetooth FW seems to be reusable be many different devices,
although (AFAIK) nobody cared to upstream it to the linux-firmware.

  reply	other threads:[~2020-04-07 16:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 19:41 [PATCH v2 0/6] Support NVIDIA Tegra-based Acer A500 and Nexus 7 devices Dmitry Osipenko
2020-04-06 19:41 ` [PATCH v2 1/6] ARM: tegra: Add device-tree for Acer Iconia Tab A500 Dmitry Osipenko
2020-04-07 10:41   ` Thierry Reding
2020-04-07 16:23     ` Dmitry Osipenko
2020-04-06 19:41 ` [PATCH v2 2/6] ARM: tegra: Add device-tree for ASUS Google Nexus 7 Dmitry Osipenko
2020-04-07 10:50   ` Thierry Reding
2020-04-06 19:41 ` [PATCH v2 3/6] dt-bindings: Add vendor prefix for Acer Inc Dmitry Osipenko
2020-04-06 19:41 ` [PATCH v2 4/6] dt-bindings: ARM: tegra: Add Acer Iconia Tab A500 Dmitry Osipenko
2020-04-06 19:41 ` [PATCH v2 5/6] dt-bindings: ARM: tegra: Add ASUS Google Nexus 7 Dmitry Osipenko
2020-04-06 19:41 ` [PATCH v2 6/6] ARM: tegra_defconfig: Enable options useful for Nexus 7 and Acer A500 Dmitry Osipenko
2020-04-07 10:08   ` Thierry Reding
2020-04-07 16:38     ` Dmitry Osipenko [this message]
2020-04-08  0:37       ` Peter Geis
2020-04-08 14:40         ` Dmitry Osipenko

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=70ad6fd6-9603-a114-2d0f-608110b68c0b@gmail.com \
    --to=digetx@gmail.com \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kwizart@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mattmerhar@protonmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=pangelo@void.io \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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).