Date: Tue, 03 May 2005 22:15:01 +0900 From: Alexander Nedotsukov <bland@FreeBSD.org> To: Roland van Laar <the_mip_rvl@myrealbox.com> Cc: gnome@FreeBSD.org Subject: Re: Fwd: Patch to gnomepilot2 for USB support under FreeBSD 5.x Message-ID: <42777955.9020105@FreeBSD.org> In-Reply-To: <1115119679.69520.5.camel@localhost> References: <1114598119.34418.19.camel@localhost.McMaster.CA> <8061fbee050429193161f9b5aa@mail.gmail.com> <8061fbee05042919363856e4bd@mail.gmail.com> <1115119679.69520.5.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Roland, The answer is native usb palm connection (-p usb:/dev/ugen0) does not work. Though you can always use slower serial over usb link. AFAIK next pilot-link release 0.13 will use libusb and get support for latest direct usb protocol changes. This probably give us a bigger chances. All the best, Alexander. Roland van Laar wrote: >Hello, > >I was quite happe when I read this email :) >I've looked into it in the past, but couldn't find an easy way to get it >"native" usb to work. > >On Fri, 2005-04-29 at 22:36 -0400, Corey Smith wrote: > > >>FYI: >> >>Here is a quick walkthrough of my setup: >> >>5.3-RELEASE >>cd /usr/ports/palm/gnomepilot2 && make install >>cd /usr/ports/mail/evolution && make -DWITH_PILOT install >>kldload uvisor >> >>gnomepilot2 uses the pilot-link package under the hood. >> >>You should be able to test pilot-link with something like: >> >>pilot-xfer --port /dev/ucom0 --list >> >>The trick is to run this command within a few seconds of pressing the >>sync button on your cradle so that /dev/ucom0 actually exists when it >>starts. If you get a list of the databases on your palm then things >>are working. >> >>My patch for gnomepilot2 simply checks for the palm device every >>timeout and then starts the conduits if it exists. >> >> > >Up to here everything works > > >>To configure evolution: >> >>Start evolution and open: Tools->Pilot settings >>Set your device to "/dev/ucom0" >>I'm able to sync at high speed without a problem: 115200 >> >> > >When I select /dev/ucom0 and serial with a speed of 9600 everything >works. Although I have to first press the hotsync button before I start >gpilotd to let it find /dev/ucom0 and sync. > > > >>You should enable the evolution conduits at this point and be able to sync. >> >>So how do you get gpilotd to startup when you start gnome? >> >>Add the pilot-applet to your gnome notification area. Then log-out >>and save your settings. Now when you login to gnome the pilot applet >>will start and startup gpilotd. >> >> > >This works :) > > > >>Then whenever you hit the hotsync >>button on your cradle a notification window will pop-up and show the >>sync status. >> >> > >The problem is that when I press the hotsync button gpilotd starts to >give these messages: > > >gpilotd-Message: Shutting down devices >gpilotd-Message: Rereading configuration... >gpilotd-Message: Watching Cradle1 (/dev/ucom0) > >/* I press the hotsync button */ > >gpilotd-Message: setting PILOTRATE=115200 > >(gpilotd:70207): gpilotd-WARNING **: pi_accept_to: Operation timed out > >(gpilotd:70207): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs >gpilotd-Message: setting PILOTRATE=115200 > >(gpilotd:70207): gpilotd-WARNING **: pi_accept_to: Operation timed out > >(gpilotd:70207): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs >gpilotd-Message: setting PILOTRATE=115200 > >(gpilotd:70207): gpilotd-WARNING **: pi_accept_to: Operation timed out > >etc > > > >>Let me know if you experience any problems. >> >> > >Let me know if you need more information. > >Roland van Laar > > > >>-Corey Smith >> >> > > >_______________________________________________ >freebsd-gnome@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-gnome >To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42777955.9020105>