From: Jactry Zeng <jactry92@gmail.com>
To: Jianfeng Liu <liujianfeng1994@gmail.com>, kaipeng94@gmail.com
Cc: andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, konradybcio@kernel.org,
krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI (SFA14-11)
Date: Mon, 12 Oct 2026 22:18:13 +0800 [thread overview]
Message-ID: <13181dfa-b92c-43b5-ae12-912abaf79c41@gmail.com> (raw)
In-Reply-To: <20261012100325.38128-1-liujianfeng1994@gmail.com>
Hi,
On 10/12/26 18:03, Jianfeng Liu wrote:
> On Mon, 12 Oct 2026 16:15:19 +0800,Kaipeng Zeng wrote:
>> Acer had a page about "Acer Swift Go Pro AI" but it was deleted,
>> fortunately here is
>> a snapshot:
>> https://web.archive.org/web/20260314171131/https://www.acer.com.cn/
>> product_list.html?parentid=323
>> It's sold in China using the name "Acer 非凡 Go Pro AI".
>> There is some discussion in the thread of my previous version:
>> https://lore.kernel.org/linux-devicetree/20260729064538.19564-3-
>> kaipeng94@gmail.com/
>> I have no idea if your "swift SFA14-11" is the same as my "Acer swift
>> Go Pro AI".
> On the naming: you're right, and thanks for the pointer — the SFA14-11
> series was indeed marketed in China as 宏碁非凡 Go Pro AI (my unit is
> an SFA14-11-QWU1; the retail listings I found, e.g. on Suning, are other
> SKUs like the SFA14-11-QGU1). One thing I noticed though: that retail page
> has since been taken down, and Acer's support sites — global and China
> alike [2] — identify the machine as plain "SFA14-11" within the Swift/非凡
> series, matching the DMI and the model string shown in Windows. So it
> looks like "Swift SFA14-11" is the stable, support-level identity, while
> "Go Pro AI" was the transient retail name.
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.
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.
As Kaipeng mentioned, there were more discussions about naming in the
threads of his v1 and v2 to this mailing list in July, if you are
interested.
next prev parent reply other threads:[~2026-10-12 14:18 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 [this message]
2026-10-13 1:57 ` [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI Jianfeng Liu
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=13181dfa-b92c-43b5-ae12-912abaf79c41@gmail.com \
--to=jactry92@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaipeng94@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=liujianfeng1994@gmail.com \
--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