From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: imx6: add support for Ka-Ro electronics TX6S-8034 module
Date: Wed, 13 Jan 2016 08:35:28 +0100 [thread overview]
Message-ID: <87h9iigce7.fsf@gmail.com> (raw)
In-Reply-To: <1452621710-15336-2-git-send-email-LW@KARO-electronics.de> ("Lothar \=\?utf-8\?Q\?Wa\=C3\=9Fmann\=22's\?\= message of "Tue, 12 Jan 2016 19:01:48 +0100")
Lothar Wa?mann <LW@KARO-electronics.de> writes:
> +/ {
> + model = "Ka-Ro electronics TX6S-8034 Module";
> + compatible = "karo,imx6dl-tx6dl", "fsl,imx6dl";
> + timestamp = __DATE__, __TIME__;
Is this needed or useful?
There's a movement that aims to do "reproducible builds" ... being
able to recompile an image and verify it against the supplied can be
helpful for security audit purposes.
> + display: display at di0 {
> + compatible = "fsl,imx-parallel-display";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_disp0_1>;
> + interface-pix-fmt = "rgb24";
> +// fsl,panel = <&lcd0_panel>;
Probably not for upstream inclusion?
next prev parent reply other threads:[~2016-01-13 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:01 [PATCH 0/3] ARM: dts: imx6: add support for more i.MX6 modules from Ka-Ro electronics Lothar Waßmann
2016-01-12 18:01 ` [PATCH 1/3] ARM: dts: imx6: add support for Ka-Ro electronics TX6S-8034 module Lothar Waßmann
2016-01-12 18:01 ` [PATCH 2/3] ARM: dts: imx6ul: add support for Ka-Ro electronics TXUL modules Lothar Waßmann
2016-01-12 18:01 ` [PATCH 3/3] ARM: dts: imx6: add display timing for NL12880BC20 display to Ka-Ro electronics TX6 LVDS modules Lothar Waßmann
2016-01-12 18:43 ` [PATCH 2/3] ARM: dts: imx6ul: add support for Ka-Ro electronics TXUL modules Fabio Estevam
2016-01-13 11:36 ` Lothar Waßmann
2016-01-13 7:35 ` Holger Schurig [this message]
2016-01-13 11:10 ` [PATCH 1/3] ARM: dts: imx6: add support for Ka-Ro electronics TX6S-8034 module Lothar Waßmann
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=87h9iigce7.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).