summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjoe <joe@FreeBSD.org>2003-11-08 11:23:07 +0000
committerjoe <joe@FreeBSD.org>2003-11-08 11:23:07 +0000
commite1f9924e1b67dd58c21ccb64722d8bb50d7fbccb (patch)
tree4c3e355b32a26de47ac8b3c7092c90b88ee06d28
parent75c2ad8b163872cd11caae4f439085e9bf7f75f4 (diff)
downloadFreeBSD-src-e1f9924e1b67dd58c21ccb64722d8bb50d7fbccb.zip
FreeBSD-src-e1f9924e1b67dd58c21ccb64722d8bb50d7fbccb.tar.gz
I've had a couple of reports that the Sony Clie_40 doesn't need the
PALM_4 initialisation hack. I've not confirmed it myself, but seeing as we already don't use it for the Sony Clie_41, let's drop it from the Clie_40 also and see what happens. (Question: What about the Clie_S360 and Clie_NX60 devices? Do we need to drop Palm4 from those as well? Possibly, but I've not had any reports about those so I don't know.) PR: kern/56575 MFC after: 3 days
-rw-r--r--sys/dev/usb/uvisor.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/dev/usb/uvisor.c b/sys/dev/usb/uvisor.c
index 72b64a4..d82cd54 100644
--- a/sys/dev/usb/uvisor.c
+++ b/sys/dev/usb/uvisor.c
@@ -217,7 +217,7 @@ static const struct uvisor_type uvisor_devs[] = {
{{ USB_VENDOR_PALM, USB_PRODUCT_PALM_TUNGSTEN_Z }, PALM4 },
{{ USB_VENDOR_PALM, USB_PRODUCT_PALM_TUNGSTEN_T }, PALM4 },
{{ USB_VENDOR_PALM, USB_PRODUCT_PALM_ZIRE }, PALM4 },
- {{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_40 }, PALM4 },
+ {{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_40 }, 0 },
{{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_41 }, 0 },
{{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_S360 }, PALM4 },
{{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_NX60 }, PALM4 },
OpenPOWER on IntegriCloud