From: Felix Becker <linux.felixbecker2@gmx.de>
To: linux-usb@vger.kernel.org
Subject: [usbserial] device 0421:069a is supported, in fact.
Date: Tue, 8 Feb 2022 13:00:48 +0100 [thread overview]
Message-ID: <20220208125958.295e8a0b@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]
Dear "linux-usb" mailing list people,
I was directed here by the email-bot of Greg Kroah-Hartman.
First I was contactim him directly, since at [1] it is written that
things regarding the `usbserial` driver should be directed to him,
which in turn I was getting from a question on where-to-address-this
which I asked here [2].
Here the issue I want to address:
I have a device which is ignored by any in-kernel driver, but when I
tell `usbserial` manually to drive that device (via
`modprobe usbserial vendor=0x0421 product=0x069a`), it provides two
serial ports where useful things can be made via the second.
It is a Nokia 130 mobile phone, and it provides an "AT"-style serial
interface where things like address book synchronisation can be made.
It has the following vendor:product number 0421:069a.
So I suggest to you to add that device as a supported device to
`usbserial`, so that hotplug works.
In `lsusb` it shows up as
`Nokia Mobile Phones 130 [RM-1035] (Charging only)`, so the string
`(Charging only)` should be removed then, too.
(The phone itself has two USB modes: "Memory card" (which will make it
behave as mass storage with access to the microSD-card) and a mode
which is called in the phone's menu as "Charging only", which is the
mode interesting here and which in fact is more than "carging only").
I have also made a Linux bugtracker issue out of this [3], but my
experience is that issues posted there are sometimes very unreliably
noticed (depending on the subsystem, some parts of the bugtracker seem
to not get attention at all). That's why I followed the suggestion in
[1] instead at first. I am still confused about what is the correct way
to give this information to the people able to deal with it properly.
[1] Linux kernel documentation "USB serial":
http://kernel.org/doc/html/latest/usb/usb-serial.html#generic-serial-driver
> For any questions or problems with this driver, please contact Greg
> Kroah-Hartman at greg@kroah.com
[2] Answer to the question where to address this on stackexchange:
http://unix.stackexchange.com/a/689577/133286
[3] Enhancement-Issue of this at the Linux bugtracker:
http://bugzilla.kernel.org/show_bug.cgi?id=215579
--
| sed 's/\([Mm]\)an[n]*/\1ensch/g'
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-02-08 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:00 Felix Becker [this message]
2022-02-08 15:20 ` [usbserial] device 0421:069a is supported, in fact Greg KH
2022-02-08 19:15 ` Felix Becker
2022-02-24 13:35 ` Johan Hovold
2022-02-24 18:28 ` Felix Becker
2022-02-26 17:47 ` Felix Becker
2022-02-28 8:51 ` Johan Hovold
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=20220208125958.295e8a0b@gmx.de \
--to=linux.felixbecker2@gmx.de \
--cc=linux-usb@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.