All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: linux-firmware@kernel.org
Cc: Rob Clark <robdclark@gmail.com>,
	Jonathan Marek <jonathan@marek.ca>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] qcom: add firmware files for Adreno A200
Date: Mon, 2 Jan 2023 18:11:23 +0200	[thread overview]
Message-ID: <54fb0621-1eb7-f7f3-08f2-1b1cf5ccdec2@linaro.org> (raw)
In-Reply-To: <20230102131443.905304-1-dmitry.baryshkov@linaro.org>

On 02/01/2023 15:14, Dmitry Baryshkov wrote:
> Add firmware files for Adreno A20x (codenamed yamato), found in
> Freescale i.MX51/i.MX53 and in some prehistoric Qualcomm Snapdragon
> SoCs.
> 
> The firmware were generated from the header files from EfikaMX kernel
> sources ([1]), which bear copyright by QUALCOMM Incorporated and have
> BSD-3-Clause licence.
> 
> [1] https://github.com/genesi/linux-legacy/tree/master/drivers/mxc/amd-gpu

For the reference, the same original files are available from CAF:

https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/mxc/amd-gpu/common?h=imx_2.6.35_maintain_caf

-- 
With best wishes
Dmitry


  reply	other threads:[~2023-01-02 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-02 13:14 [PATCH] qcom: add firmware files for Adreno A200 Dmitry Baryshkov
2023-01-02 16:11 ` Dmitry Baryshkov [this message]
2023-01-11 12:51 ` Josh Boyer
2023-01-11 15:17   ` Dmitry Baryshkov
2023-01-17 12:55     ` Josh Boyer
2023-01-17 12:56       ` Dmitry Baryshkov
  -- strict thread matches above, loose matches on Subject: below --
2019-09-04 11:26 [PATCH] qcom: Add " Fabio Estevam
2019-09-04 12:09 ` Nicolas Dechesne
2019-09-04 14:39   ` Rob Clark
2019-09-04 15:34   ` Josh Boyer
2019-09-06 15:09     ` Chris Healy
2019-09-06 15:27       ` Nicolas Dechesne

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=54fb0621-1eb7-f7f3-08f2-1b1cf5ccdec2@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=festevam@gmail.com \
    --cc=jonathan@marek.ca \
    --cc=linux-firmware@kernel.org \
    --cc=robdclark@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.