[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] FreeBSD 4.4 and USB palm m505 issues.
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 :)
thanks,
greg k-h
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.