Re: Palm and USB: 5-CURRENT, 4-CURRENT, or 4.9-RELEASE?
Jason Barnes wrote: I am trying to get my Palm Tungsten-E to sync with my FreeBSD Hi Jason, I had the interesting task of getting my Tungsten-W to sync the other week, which I succeeded with, after a few tweaks. I'm running 5.1-REL, with a couple of patches, see PRs: kern/58366 and kern/46488 You'll have to obtain the Tungsten-E product ID by doing a usbdevs -v after you've pressed the hotsync button. Then simply modify the patches in kern/58366 to reflect the E rather than the W. Apply patches and rebuild. I have the following added to my /etc/usbd.conf, above the USB device entry: # PPP for Palm Tungsten W device Palm Tungsten W devname ucom[0-9] vendor 0x0830 product 0x0031 attach /usr/sbin/ppp -auto palm; /usr/local/bin/pi-csd -H sarah -a 192.168.2.3 -n 255.255.255.0 detach killall ppp; killall pi-csd In this case sarah is the local hostname, and 192.168.2.3 is the local IP of the system. You will have to adjust the product ID here too. Oh, and be careful with the killall ppp, you might want to change that to something a bit more sophisticated :) For the /etc/ppp/ppp.conf, I have the following section: palm: set device /dev/ucom0 set cd off set dial set speed 57600 set timeout 300 set redial 5 0 set reconnect 3 5 set ctsrts on set ifaddr 192.168.2.3 192.168.2.253 enable dns open Again, 192.168.2.3 is the local IP, 192.168.2.253 is the IP assigned to the Palm. In the kernel config, I have device ucom device uvisor (or you could load it as modules I suppose) Finally, for the serial port setting in jpilot (or pilot-xfer), use the portname net:any. Unfortunately my Palm is away on repair at the moment, so I can't give you the exact details of the PPP setup of it, sorry. Follow what was outlined in the workaround, and you should get it to work (that's what I did). The important thing is that once you have set it up for LAN sync over PPP over Cradle/cable, you'll have to actually go into the HotSync app and tap the sync button there. Pressing the sync button on the cradle forces it to do a local cradle/cable sync, unfortunately. I think that includes everything I did... took me a few hours to get it all working! Now, I don't know if the Tungsten-E is running PalmOS 4 or 5. If it's 5, then there might be additional issues with the syncing, as I hear rumors saying that the hotsync protocol changed in PalmOS 5. Hope that helps... /Johny -- Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth. http://www.earthmagic.org _.' `-' `-' There is only perception. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Palm and USB: 5-CURRENT, 4-CURRENT, or 4.9-RELEASE?
I am trying to get my Palm Tungsten-E to sync with my FreeBSD 4.8-STABLE from October 23 (about a week ago). I seem not to be able to access /dev/ucom0 from pilot-xfer or jpilot, and the PPP workaround that others have suggested I can't seem to quite get working. I have heard rumors that the USB stack is fixed in newer versions such that I might be able to access the pilot directly -- can you tell me whether 4-CURRENT, 5-CURRENT, or 4.9-RELEASE might have the relevant fixes? Thank you for your help, - Jason Barnes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB and -current
It would be trivial to write a driver, like uscanner, that does the collection of two endpoints into one bidirectional file descriptor. Endpoints are the pipes that USB communicates over, and due to sloppy documentation in the USB spec. implementors of firmware didn't realise that 1-in and 1-out are different endpoints. If 1-in and 1-out would have been used, ugen0.1 could have been used bidirectionally and all would have been well. Nick On Tue, 13 Nov 2001, Peter Wemm wrote: Julian Elischer wrote: I haven't been able to find the usb mailing list where's it gone? I've been trying ot run some USB programs specifically gphoto2 and I came to the conclusion that there may be some incompatibility in the libusb layer.. since then I discovered that there are TWO libusb's.. One from NetBSD and one from the world of pinguins (Actually sourcforge) It seems to me that our libusb needs to be called libusb-hid since it only supports the HID compatible devices and the one at sourceforge should probably be called libusb. Has anyone managed to get the libusb (gpl) to work under freeBSD -current? More specifically has anyone managed to get the gphoto2 library to work? Yes. There are fundamental differences between our usb kernel stack and gphoto's assumptions. I know of one person who has made it work, I think it was Daniel O'Connor (If I remember the name right). The biggest problem was that you have to open *two* fd's to the camera (one for send, one for recieve) vs. the single fd that serial and linux use. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
USB and -current
I haven't been able to find the usb mailing list where's it gone? I've been trying ot run some USB programs specifically gphoto2 and I came to the conclusion that there may be some incompatibility in the libusb layer.. since then I discovered that there are TWO libusb's.. One from NetBSD and one from the world of pinguins (Actually sourcforge) It seems to me that our libusb needs to be called libusb-hid since it only supports the HID compatible devices and the one at sourceforge should probably be called libusb. Has anyone managed to get the libusb (gpl) to work under freeBSD -current? More specifically has anyone managed to get the gphoto2 library to work? julian -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +--x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB and -current
Julian Elischer wrote: I haven't been able to find the usb mailing list where's it gone? I've been trying ot run some USB programs specifically gphoto2 and I came to the conclusion that there may be some incompatibility in the libusb layer.. since then I discovered that there are TWO libusb's.. One from NetBSD and one from the world of pinguins (Actually sourcforge) It seems to me that our libusb needs to be called libusb-hid since it only supports the HID compatible devices and the one at sourceforge should probably be called libusb. Has anyone managed to get the libusb (gpl) to work under freeBSD -current? More specifically has anyone managed to get the gphoto2 library to work? Yes. There are fundamental differences between our usb kernel stack and gphoto's assumptions. I know of one person who has made it work, I think it was Daniel O'Connor (If I remember the name right). The biggest problem was that you have to open *two* fd's to the camera (one for send, one for recieve) vs. the single fd that serial and linux use. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
