From: Oliver Neukum <oneukum@suse.com>
To: "Рыжов Фёдор" <symansel@outlook.com>,
"Oliver Neukum" <oneukum@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] USB: cdc-acm: Add support for second ACM channel on more Nokia phones
Date: Fri, 3 Apr 2026 18:06:21 +0200 [thread overview]
Message-ID: <15d8dc67-1f2d-4df3-a7ee-2d093dd9a1c5@suse.com> (raw)
In-Reply-To: <7dcc9837-52e8-4760-b710-403d464f908f@outlook.com>
Hi,
On 03.04.26 15:20, Рыжов Фёдор wrote:
> Nokia phones have two kinds of model names: "commercial" (for example, "X3-02") and "type identifier" (my X3-02 is "RM-639"). There are cases when different phones (with different RM codes) were released under one commercial name. They look and work very similarly, but may have difference in memory amount, radio bands, SIM operator lock, region-specific SARs, etc. For example, T-Mobile branded Lumia 710 is "RM-809", but "global version" has code "RM-803".
>
> Different RM-models have different incompatible firmwares. They also have different USB PIDs. That's why there are multiple lines with same model name.
Thank you for this response. This is important information. Hence I'd
like to request that you add a general comment to the driver with your patch
giving exactly this explanation for device appearing twice. Right in front
of the declaration would be best. We really should make sure we do not
lose such information.
Regards
Oliver
next prev parent reply other threads:[~2026-04-03 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:37 [PATCH] USB: cdc-acm: Add support for second ACM channel on more Nokia phones Рыжов Фёдор
2026-03-30 10:04 ` Oliver Neukum
2026-04-03 13:20 ` Рыжов Фёдор
2026-04-03 16:06 ` Oliver Neukum [this message]
2026-03-30 13:13 ` gregkh
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=15d8dc67-1f2d-4df3-a7ee-2d093dd9a1c5@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=symansel@outlook.com \
/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