I just noticed mention of a kernel driver in your TODO file. It just happens that I'm looking at that now. My thought is to create a device file for each "function". So for the first blackberry plugged in, you'd get bbdesktop0, bbmodem0, bbjavaloader0, and so on. The serial protocol, used in the older devices and bluetooth, is basically the same as what is sent over the "RIM Desktop" socket with a different header. So if the "RIM Desktop" packets are converted to the serial format and presented on bbdesktop0, anything to do with database access is the same on /dev/ttyS0, /dev/ttyUSB0, /dev/rfcomm0, /dev/bbdesktop0. The modem from /dev/rfcomm1, /dev/bbmodem1, and so on. This would give consistent access to all of the functions, whatever the means of connection.
The same could be done in user space using a daemon and pty's. However you never know what pty is going to be assigned for what function on what device. Which means automating things like network connections is almost impossible from a user perspective, since at least one of the variables is never known in advance. A root daemon would be a little more manageable, since you could create links wherever you wanted, but you still have to deal with the blocking nature of libusb :( Not sure whether libusb is as "unpredictable" as it was when I first started this. Anyway, something to think about. I'm looking at a kernel driver for all this. My second BTW. The first turned the original mobitex blackberry's into ethernet devices, my first wireless internet connection, and my first kernel module :) It seems that RIM keeps challenging me :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
