summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/mvme16x_scsi.c
diff options
context:
space:
mode:
authorFrank Schäfer <fschaefer.oss@googlemail.com>2013-09-14 15:36:48 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-09-17 09:36:10 -0700
commit7d26a78f62ff4fb08bc5ba740a8af4aa7ac67da4 (patch)
tree43b958cc7e60bc1b37c8f9a8ff562bcf0a733db9 /drivers/scsi/mvme16x_scsi.c
parentdfe2902032ac9f8899214767dc5bc172254838ad (diff)
downloadop-kernel-dev-7d26a78f62ff4fb08bc5ba740a8af4aa7ac67da4.zip
op-kernel-dev-7d26a78f62ff4fb08bc5ba740a8af4aa7ac67da4.tar.gz
USB: pl2303: distinguish between original and cloned HX chips
According to Prolific, several (unauthorized) cheap and less functional clones of the PL2303HX chip are in circulation. [1] I've had the chance to test such a cloned device and it turned out that it doesn't support any baud rates above 115200 baud (original: 6 Mbaud) It also doesn't support the divisior based baud rate encoding method, so no continuous baud rate adjustment is possible. Nevertheless, these devices have been working (unintentionally) with the driver up to commit 61fa8d694b ("pl2303: also use the divisor based baud rate encoding method for baud rates < 115200 with HX chips"), and this commit broke support for them. Fortunately, it is pretty simple to distinguish between the original and the cloned HX chips, so I've added a check and an extra chip type to keep the clones working. The same check is used by the latest Prolific Windows driver, so it should be solid. [1] http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/scsi/mvme16x_scsi.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud