aboutsummaryrefslogtreecommitdiff
path: root/net/rds/bind.c
diff options
context:
space:
mode:
authorRussell Lang <gsview@ghostgum.com.au>2009-07-17 19:29:20 +1000
committerGreg Kroah-Hartman <gregkh@suse.de>2009-07-28 14:31:10 -0700
commit9d498beafc0a66ce333f0d9067af0aa5dedd4c8e (patch)
treef8d2302086de6d7a1698cd59f12022111e5d4f9d /net/rds/bind.c
parentf1469fc3ef1d5a8a67146c1c72021f012a59dea6 (diff)
USB: aten uc2324 is really a moschip 7840
I've opened up the case, and the chips in the ATEN UC2324 are: Moschip MCS7840CV-AA 69507-6B1 0650 (USB to 4-port serial) (logo with AF kerned together) 0748 24BC02 SINGLP (unknown 8-pin chip) (logo looks like 3 or Z in circle) ZT3243LEEA 0752 B7A16420.T (4 chips, so this will be RS232 line driver) (Probably equivalent of Sipex SP3243) So the ATEN 2324 (aten2011.c driver), is definitely the Moschip 7840, and should use the mos7840.c driver. I expect you will remove the aten2011.c driver from the staging area. From the aten2011.c source code, the device ID for the UC2322 (2 port serial) is 0x7820, just like the Moschip evaluation board. This value should be added to the device id table of mos7840.c. Here's a patch that adds these devices to the driver. From: Russell Lang <gsview@ghostgum.com.au> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'net/rds/bind.c')
0 files changed, 0 insertions, 0 deletions