On Tue, 2008-01-08 at 17:49 +0000, Mark Ellis wrote: > 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.
This is fit! Go you! I will definitely be using this soon. > 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. Ah I see, you legacy boys! -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- 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
