From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_SOC_IMX6Q = i.MX6 Quad/DualLite/Solo
Date: Wed, 06 Oct 2021 10:17:52 +0200 [thread overview]
Message-ID: <m3ee8ymurz.fsf@t19.piap.pl> (raw)
In-Reply-To: <8d54835921f1648a4d50d8d4e160b5a12582590f.camel@pengutronix.de> (Lucas Stach's message of "Wed, 06 Oct 2021 09:36:05 +0200")
Lucas Stach <l.stach@pengutronix.de> writes:
>> Print i.MX6 "Solo" name in addition to the "Quad" and "DualLite"
>> for SOC_IMX6Q.
>>
> I don't think that's helpful, you would need to at least also print
> "Dual" to make it correct. The Solo is just a fused down version of the
> DualLite, just as the Dual is a fused down version of the Quad.
>
> Quad/DualLite refers to the two different die versions of the chip.
Perhaps we need to print Dual as well.
ATM "cat /proc/cpuinfo" (and everything using it) prints "Freescale
i.MX6 Quad/DualLite (Device Tree)" on Solo and this is, at best,
misleading: making people wonder what CPU do they really have.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
prev parent reply other threads:[~2021-10-06 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 6:04 [PATCH] CONFIG_SOC_IMX6Q = i.MX6 Quad/DualLite/Solo Krzysztof Hałasa
2021-10-06 6:17 ` Ahmad Fatoum
2021-10-06 7:36 ` Lucas Stach
2021-10-06 8:17 ` Krzysztof Hałasa [this message]
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=m3ee8ymurz.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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