After upgrading to 4.7-R on our Toshiba Satellite Pro 4600 recently,
we gave a closer look at the ucom(4) & uvisor(4) USB devices
to connect with our Palm m130 USB cradle.

A quick inspection of the kernel sources suggested the following additions:

/usr/src/sys/dev/usb/usbdevs:
 product PALM M125              0x0040  Palm m125
+product PALM M130              0x0050  Palm m130

/usr/src/sys/dev/usb/uvisor.c:
        {{ USB_VENDOR_PALM, USB_PRODUCT_PALM_M125 }, PALM4 },
+       {{ USB_VENDOR_PALM, USB_PRODUCT_PALM_M130 }, PALM4 },
        {{ USB_VENDOR_SONY, USB_PRODUCT_SONY_CLIE_40 }, PALM4 },

And the relevant USB entries included in the kernel configuration:
device usb
device uhci
device ucom
device uvisor

A new kernel was compiled, installed, & the system restarted.
Following that, an entry in /dev/ was made:

        # cd /dev; ./MAKEDEV ucom0; ls -l /dev/ucom0
crw-------  1 xyz xyz    138, 128 Dec 27 00:44 /dev/ucom0

and...
        <USB Cradle HotSync Button Pressed>
ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 5
ucom0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 5

The kernel appears to find the Palm & its USB cradle, as noted above.
        $ usbdevs -v

Controller /dev/usb0:
addr 1: self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
 port 2 addr 3: power 64 mA, config 1, Standard USB Hub(0x3301), Atmel(0x03eb), rev 
3.00
  port 4 addr 5: self powered, config 1, Palm Handheld(0x0050), Palm, Inc.(0x0830), 
rev 1.00

Then, with a freshly-compiled pilot-link (0.11.6),
running pilot-xfer(1) to list the device contents, however, fails:
        $ pilot-xfer -p /dev/ucom0 -l
ucom0: ucomreadcb: IOERROR
ucom0: at uhub1 port 4 (addr 5) disconnected
ucom0: still open, focing close
ucom0: detached

Running pilot-xfer(1) with the serial cradle works fine at 115,200bps,
so we assume pilot-link is not the problem here.

I don't mind using the serial cradle at home
(we still need it on the Sun Blade in the office),
but it would be nice to get the USB cradle to work.

Any suggestions on what we might look at next ?
--
Gary E. RAFE, Ph.D.
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to