Date: 27 Oct 2002 07:56:15 -0600 From: Larry Rosenman <ler@lerctr.org> To: "G.E. Rafe" <rafege@mail.com> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: coldsync-2.2.5 w/Palm m130 via USB ? Message-ID: <1035726976.390.5.camel@lerlaptop.lerctr.org> In-Reply-To: <200210270407.AAA16668@strange.eng.utoledo.edu> References: <200210270407.AAA16668@strange.eng.utoledo.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2002-10-26 at 23:07, G.E. Rafe wrote:
> !Sure, here we go:
> !Sep 27 16:06:55 piglet /kernel: ucom0: Palm, Inc. Palm Handheld, rev
> !1.00/1.00, addr 3
> !
> !> Or give more info...
> !> this is my output.
> !> Kernel has : ucom, uplcom and uvscom devices/support
> !> Sep 27 13:04:51 dori /kernel: ugen0: Palm, Inc. Palm Handheld, rev
> !> 1.00/1.00, addr 2
> !
> !It is important that you don't let the ugen driver get the device.
> !This means you either should load uvisor (kldload uvisor) prior to
> !pressing the sync button (for e.g. in /etc/rc.local) or you should
> !configure usbd to load the driver (which means the first sync will
> !fail - or at least I don't know how to do it ;).
> !
> !Put the following lines in /etc/usbd.conf for the second approach:
> !device "Palm m125"
> ! vendor 0x830
> ! product 0x0040
> ! release 0x0100
> ! attach "if ! kldstat -n uvisor > /dev/null 2>&1 ; then kldload uvisor; fi"
>
> Hank -- We just upgraded our Toshiba Satellite Pro 4600 to 4.7-R
> and gave our USB-connected Palm m130 cradle a go with the information
> you forwarded earlier.
>
> With devices "ucom" & "uvisor" compiled into the kernel,
> we still get the ugen0 connection when the HotSync button is pressed:
>
> ugen0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 5
>
> With the Palm device connected, "usbdevs -v" returns:
>
> port 4 addr 5: self powered, config 1, Palm Handheld(0x0050), Palm, Inc.(0x0830), rev 1.00
>
> Following your original suggestion, we took the ucom & uvisor devices
> out of the kernel, recompiled, and updated /etc/usbd.conf with
> "product 0x0050", as noted in usbdevs.
>
> Pressing the HotSync button loads the ucom & uvisor kernel modules OK,
> but ugen continues to pick it up, instead !
>
> I suppose the next step is to build a kernel without "ugen" & see how
> the kernel reacts to the HotSync button.
>
> Perhaps there's still another trick to force a connection with ucom/uvisor.
did you change the usbd.conf entry to say ucom?
There are also issues with the usb stuff with Pilot-Link (the pilot-link
guys are working on it).
Here is my usbd.conf entry for a ucom connected M515:
device "Palm Handheld"
devname "ucom0"
vendor 0x0830
product 0x0003
release 0x0100
# attach "/home/ler/bin/pilot-sync.sh ${DEVNAME}"
mangle to taste.
Also, did someone fix the coldsync port to actually enable the USB
stuff?
LER
> --
> Gary E. RAFE, PhD
> grafe@eng.utoledo.edu
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-mobile" in the body of the message
>
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1035726976.390.5.camel>