From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: jactry92@gmail.com
Cc: andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, kaipeng94@gmail.com,
konradybcio@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, liujianfeng1994@gmail.com,
robh@kernel.org, krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI
Date: Tue, 13 Oct 2026 09:57:27 +0800 [thread overview]
Message-ID: <20261013015728.43307-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <13181dfa-b92c-43b5-ae12-912abaf79c41@gmail.com>
Hi,
On Mon, 12 Oct 2026 22:18:13 +0800, Jactry Zeng wrote:
>I think we are about confusing the product name and the model name here?
>It is clear that the product name is Acer Swift (aka '非凡' in Chinese) Go
>Pro AI; the link to Ubuntu stubble you provided also reveals this somehow.
I agree the product name / model name distinction is the right frame. It
turns out we can settle the product name fairly directly, though: if I look
my machine up on Acer's support site by its SNID, it resolves to
"Swift SFA14-11" in every region I tried — Japan, US, Australia, UK —
and on the China support site as well. So within Acer's support database
the product name is uniformly "Swift SFA14-11", and "非凡 Go Pro AI" was
only the retail marketing name used on the Chinese storefront, whose page
has since been taken down. It is not even a China-vs-global split — the
support identification is the same everywhere.
>Also, IMHO, I think we can't use 'stable' to describe this situation. As
>soon as the product is produced, it was given a product/model name;
>unless Acer renames it, this is it. The vendor can also remove the
>support page that you referred to sometime in the future, just like they
>removed the product page; this isn't rare; I think we always shouldn't
>depend on it.
I fully agree that web pages are not a sound basis — so I'm happy to drop
page-based arguments altogether. That leaves the two sources that cannot be
taken down: the DMI tables provided by the firmware (Product Name:
SFA14-11, which is also what Windows displays as the model) and the SNID
label physically on the machine (SFA14-11-QWU1 on my unit). Both are
model-name only.
I think the resolution follows from the product/model split itself: the
model property is human-readable free text, and per the conventions in tree
(e.g. "Dell XPS 13 9345", "Lenovo ThinkPad T14s Gen 6") it is free to carry
the marketing name — so something like "Acer Swift Go Pro AI (SFA14-11)"
works fine there, and users who bought it as 非凡 Go Pro AI can recognize
their machine by it. The compatible, on the other hand, is the machine
identifier, and it should correspond to what the firmware reports —
either the model-only "acer,sfa14-11" (my v1, following the DMI) or family
+ model "acer,swift-sfa14-11" (what the maintainers asked me to use on my
series). I'd rather not embed a retail marketing name in the compatible.
I'll leave the final call to the maintainers.
Best regards,
Jianfeng
prev parent reply other threads:[~2026-10-13 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:54 [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI (SFA14-11) Kaipeng Zeng
2026-10-06 8:54 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Add " Kaipeng Zeng
2026-10-06 8:54 ` [PATCH v4 2/2] arm64: dts: qcom: Add support for " Kaipeng Zeng
2026-10-06 9:07 ` sashiko-bot
2026-10-08 10:34 ` [PATCH v4 0/2] Add device tree " Jianfeng Liu
2026-10-12 8:15 ` Kaipeng Zeng
2026-10-12 10:03 ` Jianfeng Liu
2026-10-12 14:18 ` Jactry Zeng
2026-10-13 1:57 ` Jianfeng Liu [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=20261013015728.43307-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jactry92@gmail.com \
--cc=kaipeng94@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@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