From: Johan Hovold <johan@kernel.org>
To: Jan-Niklas Burfeind <kernel@aiyionpri.me>
Cc: Dmytro Bagrii <dimich.dmb@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
Frank A Kingswood <frank@kingswood-consulting.co.uk>,
Frank Zago <frank@zago.net>
Subject: Re: [PATCH] Revert "USB: serial: ch341: add new Product ID for CH341A"
Date: Mon, 21 Feb 2022 09:49:09 +0100 [thread overview]
Message-ID: <YhNSBTT9dTK3gffb@hovoldconsulting.com> (raw)
In-Reply-To: <7e80c8cf-5940-c5b3-89d9-e4e7e53a380c@aiyionpri.me>
On Thu, Feb 10, 2022 at 11:18:22AM +0100, Jan-Niklas Burfeind wrote:
> Hello everyone.
>
> For now I can identify two different USB-IDs depending on the Jumper
> position on the board:
>
> 1-2 connected: idVendor=1a86, idProduct=5512
> 2-3 or none : idVendor=1a86, idProduct=5523
>
> I'm not sure how I'd plug it to reach the Parallel Printer Interface
> mentioned before.
>
> The advertised position of this Jumper is 1-2.
> Both positions are labeled with two different chinese symbols, "2-3" is
> labeled with TTL as well.
>
> Looking at the devices schematics I think its safe to revert my original
> commit and I'm sorry to have caused you all this trouble.
>
> At the time I added the device I missidentified the Jumper as voltage
> level selector.
>
> I had seen others using the board on youtube, with Jumper position 1-2;
> and did not understand, why my system would not recognize it at all.
>
>
> Sorry again and thanks for the effort
No problem. Thanks for helping us clear this up.
Johan
next prev parent reply other threads:[~2022-02-21 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 0:08 [PATCH] Revert "USB: serial: ch341: add new Product ID for CH341A" Dmytro Bagrii
2022-02-08 10:34 ` Greg KH
2022-02-08 13:34 ` Dmytro Bagrii
2022-02-09 14:18 ` Johan Hovold
2022-02-09 17:24 ` Jan-Niklas Burfeind
2022-02-10 5:41 ` Dmytro Bagrii
2022-02-21 8:48 ` Johan Hovold
2022-02-10 10:18 ` Jan-Niklas Burfeind
2022-02-21 8:49 ` Johan Hovold [this message]
2022-02-10 16:41 ` [PATCH v2] " Dmytro Bagrii
2022-02-21 9:02 ` 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=YhNSBTT9dTK3gffb@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=dimich.dmb@gmail.com \
--cc=frank@kingswood-consulting.co.uk \
--cc=frank@zago.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@aiyionpri.me \
--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.