From owner-freebsd-mobile Sun Oct 27 5:56:21 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5397637B406 for ; Sun, 27 Oct 2002 05:56:18 -0800 (PST) Received: from lerlaptop.lerctr.org (lerlaptop.lerctr.org [207.158.72.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7336543E3B for ; Sun, 27 Oct 2002 05:56:17 -0800 (PST) (envelope-from ler@lerctr.org) Received: from localhost (localhost [127.0.0.1]) by lerlaptop.lerctr.org (8.12.6/8.12.6) with ESMTP id g9RDuFF5000601; Sun, 27 Oct 2002 07:56:16 -0600 (CST) (envelope-from ler@lerctr.org) Subject: Re: coldsync-2.2.5 w/Palm m130 via USB ? From: Larry Rosenman To: "G.E. Rafe" Cc: freebsd-mobile@FreeBSD.ORG In-Reply-To: <200210270407.AAA16668@strange.eng.utoledo.edu> References: <200210270407.AAA16668@strange.eng.utoledo.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 27 Oct 2002 07:56:15 -0600 Message-Id: <1035726976.390.5.camel@lerlaptop.lerctr.org> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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