Greg KH wrote:
> > I trust it will. I do appreciate the effort. If there's anythinh I can
> > do to help, let me know. Is my former idea (kernel driver that reads
> > from USB and presents a tty device without additional hardware, even
> > if the tty is m505-specific) even technically possible? I don't know
> > all that much about USB.
>
> Yes it is possible, it's how the Visor driver works :)
But the m50[05] speaks another protocol, right? I figured I'd give
usbserial (with vendor/device params) and the visor module a go, but I
didn't get either to work.
> For the m505 and m500, they striped out one layer of the Palm protocol
> due to them relying on the USB protocol.
So the clip-on connect thingy 'speaks' USB natively?
> The kernel driver could add
> that layer back on to the data, making no changes to pilot-link
> necessary, but that is better off to be done in pilot-link, rather than
> in the kernel. Did that make sense?
Ayup. But I'd still like to see this in a kernel driver, if possible.
Besides wanting to sync to pilot-link, I have to sync to outlook too
(company standard). Since I primarily use GNU/Linux, I've installed
VMWare so I can do these things. Formerly I could just sync in VMWare
since serial ports are passed through. Since VMWare has no USB
support, and none planned, a tty device that coughs up the data that
the palm emits would allow me to use my setup as usual.
Emile
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-users
