Re: [coldsync-hackers] FreeBSD 4.4 and USB palm m505 issues.

[Josef Karthauser <joe@tao.org.uk>]

On Tue, Nov 27, 2001 at 12:35:40PM -0800, Greg KH wrote:
> On Tue, Nov 27, 2001 at 11:13:22AM -0800, David A. Desrosiers wrote:
> > 
> > > On FreeBSD, coldsync is directly talking to the USB interface.
> > 
> > 	Is there a reason (kernel, userspace, device) that FreeBSD talks to
> > the native USB interface, and Linux must talk to a userspace serial device?
> > Not that I'm arguing that approach of course, just curious. I don't yet know
> > the innards of the *BSD kernel architecture yet.
> 
> Linux doesn't really need the kernel driver either, as Johannes has
> proven with his patch to use libusb in coldsync (see the archives.)  I
> wrote the kernel driver so user space programs (like coldsync and
> pilot-xfer) would not need to be changed, as the original USB visor was
> just passing the standard sync data over the USB connection.  Palm has
> changed things due to the 4.0 changes to the protocol.
> 
> So, if you are willing to use libusb for pilot-xfer, I'd be glad to drop
> the visor driver from the kernel :)

I'm happy to port uvisor to FreeBSD, on the other hand if
coldsync/4.0/usb works with libusb on linux we should port the
differences to FreeBSD too.  I don't care as long as I can get my m505
to sync somehow.

Joe

PGP signature