>>>>> "Greg" == Greg KH <[EMAIL PROTECTED]> writes:

Jack> I prefer the first option, since any modifications to Linux
Jack> device drivers will not assist users of other Unixes like
Jack> FreeBSD.

Greg> But from what I remember about the current *BSD situation with
Greg> the USB Visor, it doesn't work with the current pilot-link
Greg> package due to the way the driver author implemented the user
Greg> interface.  But coldsync does work with a special flag option.

Yes.  This seems to me to be the right way to go, as I mentioned in my
previous message to the list.

Greg> Originally both the FreeBSD author and I worked to get the Visor
Greg> protocol figured out a few years ago, but we diverged when it
Greg> came to the final implementation (I wanted the device to look
Greg> like a serial port, so the current tools would work with no
Greg> modification, and he worked with the coldsync author to tweak it
Greg> to work properly.)

Greg> Is this still true?

I haven't yet tried to sync my M505 via USB as the machine I do most
of my syncing on doesn't have serial.  I will go check it out and get
back to the list.

Jack> (don't forget about the non-Linux unixes, please!)

Greg> I don't, but I don't have a say in how the USB driver works for
Greg> other platforms. :)

You shouldn't have to, if I understand correctly.  All pilot-xfer
needs to know is whether it's a USB or serial device (to speak the
right lower-level protocols) and what device file to use.  In an ideal
world, the driver would just drive -- pushing and pulling bytes in an
application-invisible manner.

Jack.
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix

Reply via email to