Greg KH wrote:
> I understand your wanting this all in a kernel driver, but don't push
> something into kernel space that can be done just as easily in
> userspace.
>
> A kernel driver is needed to handle the USB protocol, that's it. As
> there are patches to pilot-link to handle the new m500 and m505
> protocols, and pilot-link is portable to almost every platform out
> there, I'm not going to duplicate that logic in the kernel.
If it can, thet's perfectly fine for me. If not, I'll just hack my own
private kernel driver. Free Software at work. I don't expect this
driver to be in the generic kernel release.
> To solve your VMWare/Outlook problem, I would suggest getting a serial
> cradle.
Not available here at this moment. I'll probably get the IrDA stuff to
work, but if I can save the expense of an extra cradle with a software
hack, I'll happily do so. I'm not expecting this to be widely useful
since most people will just use straight pilot-link, so I'm not
exactly expecting anyone to do this work for me.
It's been a while since I used pipes -- can pipes be bi-directional?
Could I just use pilot-link (once it digs the m50x) to 'talk serial'
trhough a named pipe?
Emile
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-users
