linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: linux-firmware@kernel.org
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: linux-firmware: add firmware for Lontium lt9611uxc DSI to HDMI bridge
Date: Fri, 11 Dec 2020 03:46:10 +0300	[thread overview]
Message-ID: <X9LBUn5KIKVKQGlI@eriador.lumag.spb.ru> (raw)

Hello linux-firmware maintainers,

The following changes since commit 7455a36066741a6e52fba65e04f6451b4cdfd9c4:

  Merge branch 'guc_v49' of git://anongit.freedesktop.org/drm/drm-firmware into main (2020-11-30 09:26:11 -0500)

are available in the Git repository at:

  https://github.com/lumag/linux-firmware lt9611uxc

for you to fetch changes up to 63ab3db8399a504048716eb3feed2867da58876a:

  linux-firmware: add firmware for Lontium LT9611UXC DSI to HDMI bridge (2020-12-11 03:27:38 +0300)

----------------------------------------------------------------
Dmitry Baryshkov (1):
      linux-firmware: add firmware for Lontium LT9611UXC DSI to HDMI bridge

 LICENSE.Lontium  |   2 ++
 WHENCE           |   8 ++++++++
 lt9611uxc_fw.bin | Bin 0 -> 17932 bytes
 3 files changed, 10 insertions(+)
 create mode 100644 LICENSE.Lontium
 create mode 100644 lt9611uxc_fw.bin

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: linux-firmware@kernel.org
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: linux-firmware: add firmware for Lontium lt9611uxc DSI to HDMI bridge
Date: Fri, 11 Dec 2020 03:46:10 +0300	[thread overview]
Message-ID: <X9LBUn5KIKVKQGlI@eriador.lumag.spb.ru> (raw)
Message-ID: <20201211004610.ycko_OUWFr0bRiPdsly6XUVOG1Udt0HasRHX_Zu0q3U@z> (raw)

Hello linux-firmware maintainers,

The following changes since commit 7455a36066741a6e52fba65e04f6451b4cdfd9c4:

  Merge branch 'guc_v49' of git://anongit.freedesktop.org/drm/drm-firmware into main (2020-11-30 09:26:11 -0500)

are available in the Git repository at:

  https://github.com/lumag/linux-firmware lt9611uxc

for you to fetch changes up to 63ab3db8399a504048716eb3feed2867da58876a:

  linux-firmware: add firmware for Lontium LT9611UXC DSI to HDMI bridge (2020-12-11 03:27:38 +0300)

----------------------------------------------------------------
Dmitry Baryshkov (1):
      linux-firmware: add firmware for Lontium LT9611UXC DSI to HDMI bridge

 LICENSE.Lontium  |   2 ++
 WHENCE           |   8 ++++++++
 lt9611uxc_fw.bin | Bin 0 -> 17932 bytes
 3 files changed, 10 insertions(+)
 create mode 100644 LICENSE.Lontium
 create mode 100644 lt9611uxc_fw.bin
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2020-12-11  0:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  0:46 Dmitry Baryshkov [this message]
2020-12-11  0:46 ` linux-firmware: add firmware for Lontium lt9611uxc DSI to HDMI bridge Dmitry Baryshkov
2020-12-18 19:06 ` Josh Boyer
2020-12-18 19:06   ` Josh Boyer

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=X9LBUn5KIKVKQGlI@eriador.lumag.spb.ru \
    --to=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-firmware@kernel.org \
    /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).