From: Dax Kelson <Dax@GuruLabs.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test7 PATCH] Handspring Treo 600 id
Date: Thu, 09 Oct 2003 13:34:50 -0600 [thread overview]
Message-ID: <1065728090.2843.19.camel@mentor.gurulabs.com> (raw)
I've got a new toy. This obviously correct 4 liner patches
the two files:
drivers/usb/serial/visor.c
drivers/usb/serial/visor.h
Works like a champ here. Linus, please apply.
diff -ur linux-2.6.0-test7-treo600/drivers/usb/serial/visor.c linux-2.6.0-test7/drivers/usb/serial/visor.c
--- linux-2.6.0-test7-treo600/drivers/usb/serial/visor.c 2003-10-09 13:26:41.000000000 -0600
+++ linux-2.6.0-test7/drivers/usb/serial/visor.c 2003-10-09 13:26:18.000000000 -0600
@@ -201,6 +201,8 @@
.driver_info = (kernel_ulong_t)&palm_os_3_probe },
{ USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_TREO_ID),
.driver_info = (kernel_ulong_t)&palm_os_4_probe },
+ { USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_TREO600_ID),
+ .driver_info = (kernel_ulong_t)&palm_os_4_probe },
{ USB_DEVICE(PALM_VENDOR_ID, PALM_M500_ID),
.driver_info = (kernel_ulong_t)&palm_os_4_probe },
{ USB_DEVICE(PALM_VENDOR_ID, PALM_M505_ID),
@@ -247,6 +249,7 @@
static struct usb_device_id id_table_combined [] = {
{ USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_VISOR_ID) },
{ USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_TREO_ID) },
+ { USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_TREO600_ID) },
{ USB_DEVICE(PALM_VENDOR_ID, PALM_M500_ID) },
{ USB_DEVICE(PALM_VENDOR_ID, PALM_M505_ID) },
{ USB_DEVICE(PALM_VENDOR_ID, PALM_M515_ID) },
diff -ur linux-2.6.0-test7-treo600/drivers/usb/serial/visor.h linux-2.6.0-test7/drivers/usb/serial/visor.h
--- linux-2.6.0-test7-treo600/drivers/usb/serial/visor.h 2003-10-09 13:26:50.000000000 -0600
+++ linux-2.6.0-test7/drivers/usb/serial/visor.h 2003-10-09 13:26:22.000000000 -0600
@@ -20,6 +20,7 @@
#define HANDSPRING_VENDOR_ID 0x082d
#define HANDSPRING_VISOR_ID 0x0100
#define HANDSPRING_TREO_ID 0x0200
+#define HANDSPRING_TREO600_ID 0x0300
#define PALM_VENDOR_ID 0x0830
#define PALM_M500_ID 0x0001
reply other threads:[~2003-10-09 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1065728090.2843.19.camel@mentor.gurulabs.com \
--to=dax@gurulabs.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®