On Tue, 2008-01-08 at 17:29 +0000, Jonny Lamb wrote: > On Mon, 2008-01-07 at 19:29 +0000, Mark Ellis wrote: > > I've committed my attempt at this for your delight and delectation, if > > anyone wants to give it a go it would be much appreciated. > > Wow, interested! I'm not actually very sure what this is, but I'm still > interested! A short description would be nice..?! :-) I shall definitely > give it a go once my todo list is slightly shorter! >
It's a hal callout framework with compatible dccm. That sounds good and means nothing doesn't it :) This is what John Carr and myself have been discussing. Ok, more usefully, it installs a hal fdi (device information file) for WM devices, currently set to recognise devices by rndis_host or ipaq driver information, or "pocketpc" string for rndis-ng (like odccm). When hal discovers one of these it calls a script to bring up the interface, be it rndis or ppp, which then calls the dccm. This does pretty much what every dccm we have had does, but via hal. The device information is published as hal properties rather than over dbus (well hal is over dbus anyway, but you get my meaning), so if you look at the device in hal-device-manager you'll see properties, prefixed pda.pocketpc, such as name, os version and model. The methods to obtain a rapi connection and provide a password are the same, but through a hal interface rather than our own, these are passed through to dccm by hal. Each device also gets its own dccm, which terminates when hal detects the device is disconnected, so no redundant processes or boot scripts. Note, multi device won't work yet, gnet is being wierd with binding to a specific interface, but I will be able to fix this eventually. > > The idea is it should just work, no config required. I've had my WM2003 > > device connected and able to respond to rapi calls. First remove > > anything else that will interfere, like udev rules etc. Feedback on WM5 > > would be great. > > By "no config required", what config do you speak of? After all, getting > to the stage of being able to "pls" to one's phone is rather config-less > is it not? > Mostly referring to pre WM5, the serial stuff is all figured out on the fly. Also as mentioned above, dccm will fire up when required, it doesn't need a boot script or user intervention. > > You will need a patched libsynce and librapi, use the provided patches > > in the 'patches' dir. I didn't want to commit these until after Jonny > > releases 0.11. > > Thank you for understanding this..! > No worries :) It's all backwards compatible and unlikely to break, but wasn't worth the hassle yet. With the small patches to libsynce and librapi, anything using pure rapi calls won't notice any difference. Anything that needs more direct access will only need minor fixes to call hal instead of odccm. For C applications libhal does the job splendidly. I haven't found an equivalent for python, but it's just a case of tweaking the dbus interface we use. If Guido and Dr John are reading, I found a nice example at http://davyd.livejournal.com/206645.html All logging goes to syslog local5 if you want to keep an eye on things. At the moment it'll spurt out various amounts of experimental stuff as well. Mark ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
