mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andree Leidenfrost <aleidenf@bigpond.net.au>
To: linux-kernel@vger.kernel.org
Subject: Problem: Palm Tungsten T + kernel 2.4.20 + Tungsten patch applied
Date: 21 Feb 2003 21:45:12 +1100	[thread overview]
Message-ID: <1045824312.1404.37.camel@aurich.ostfriesland> (raw)

Dear list

I'm having the above problem. In detail, when pressing the hotsync
button, /var/log/syslog says:

Feb 21 21:15:30 aurich kernel: hub.c: new USB device 00:10.0-1, assigned
address 3
Feb 21 21:15:30 aurich kernel: usb.c: USB device 3 (vend/prod
0x830/0x60) is not claimed by any active driver.
Feb 21 21:15:33 aurich /etc/hotplug/usb.agent: Setup visor for USB
product 830/60/100
Feb 21 21:15:33 aurich kernel: usb.c: registered new driver serial
Feb 21 21:15:33 aurich kernel: usbserial.c: USB Serial Driver core v1.4
Feb 21 21:15:33 aurich kernel: usbserial.c: USB Serial support
registered for Handspring Visor / Palm 4.0 / Clié 4.x
Feb 21 21:15:33 aurich kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter detected
Feb 21 21:15:36 aurich kernel: usb_control/bulk_msg: timeout
Feb 21 21:15:36 aurich kernel: visor.c: visor_startup - error getting
connection information
Feb 21 21:15:36 aurich kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Feb 21 21:15:36 aurich kernel: usbserial.c: Handspring Visor / Palm 4.0
/ Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Feb 21 21:15:36 aurich kernel: usbserial.c: USB Serial support
registered for Sony Clié 3.5
Feb 21 21:15:36 aurich kernel: visor.c: USB HandSpring Visor, Palm m50x,
Sony Clié driver v1.6
Feb 21 21:15:36 aurich kernel: usb-uhci.c: interrupt, status 2, frame#
1431
Feb 21 21:15:36 aurich kernel: usbdevfs: USBDEVFS_CONTROL failed dev 3
rqt 128 rq 6 len 0 ret -32
Feb 21 21:15:36 aurich kernel: usbdevfs: USBDEVFS_CONTROL failed dev 3
rqt 128 rq 6 len 0 ret -32

I have applied the following patches:

--- visor.c.orig	Wed Feb 19 22:55:38 2003
+++ visor.c	Wed Feb 19 22:57:00 2003
@@ -174,6 +174,7 @@
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_I705_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_M125_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_M130_ID) },
+	{ USB_DEVICE(PALM_VENDOR_ID, PALM_TUNGSTEN_T_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_ZIRE_ID) },
 	{ USB_DEVICE(HANDSPRING_VENDOR_ID, HANDSPRING_VISOR_ID) },
 	{ USB_DEVICE(SONY_VENDOR_ID, SONY_CLIE_4_0_ID) },
@@ -195,6 +196,7 @@
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_I705_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_M125_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_M130_ID) },
+	{ USB_DEVICE(PALM_VENDOR_ID, PALM_TUNGSTEN_T_ID) },
 	{ USB_DEVICE(PALM_VENDOR_ID, PALM_ZIRE_ID) },
 	{ USB_DEVICE(SONY_VENDOR_ID, SONY_CLIE_3_5_ID) },
 	{ USB_DEVICE(SONY_VENDOR_ID, SONY_CLIE_4_0_ID) },


--- visor.h.orig	Wed Feb 19 22:57:20 2003
+++ visor.h	Wed Feb 19 22:58:04 2003
@@ -27,6 +27,7 @@
 #define PALM_I705_ID			0x0020
 #define PALM_M125_ID			0x0040
 #define PALM_M130_ID			0x0050
+#define PALM_TUNGSTEN_T_ID		0x0060
 #define PALM_ZIRE_ID			0x0070
 
 #define SONY_VENDOR_ID			0x054C

Also I have added the following line to /etc/hotplug/usb.usermap:
visor                0x0003      0x0830   0x0060    0x0000      
0x0000       0x00         0x00            0x00           
0x00            0x00               0x00               0x00000000

I do not think it matters at this stage, but I'm running pilot-link
0.11.7 and jpliot 0.99.4 on Debian woody.

Syncing my m505 works fine, but I'd love to be able to sync my new and
shiny Tungsten T... ;-)

I have searched google and found this patch and success messages of
other people but no clue as to what my problem could.

Cheers
Andree
-- 
Andree Leidenfrost
Sydney - Australia


             reply	other threads:[~2003-02-21 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 10:45 Andree Leidenfrost [this message]
2003-02-21 14:43 ` Greg KH
2003-02-23  9:36 Andree Leidenfrost

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=1045824312.1404.37.camel@aurich.ostfriesland \
    --to=aleidenf@bigpond.net.au \
    --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®