>> Aside from that the major remaining issue is the infamous John Carr >> Dirty Patch, which he claims to be getting free time to work on this >> week ;). If that could be cleaned up and upstreamed, I think we'd be in >> good shape in terms of the upstream kernel doing everything synce needs. >> Right? Or did I miss anything? >> -- >> adamw >> > > You guys have too much fun on #synce :) You've got me intrigued about > the Dirty Patch... > > Mark
The dirty patch, the thing of legends. It exists in SVN here: http://synce.svn.sourceforge.net/svnroot/synce/trunk/patches/usb-rndis-lite-samsung.patch As you can see, i force debug on because i have no idea whether the patch is sane or not and i want all the debug info i can get. The reason I consider it dirty is that it needs the rndis_get_in_endpoint function which is called every time something calls rndis_command. Ideally that should run once when the driver loads for a given device, but i felt like i was being too invasive when I started doing that and whimped out. The patch exists through careful comparison of the deprecated user mode and the current kernel mode implementations of usb-rndis, the poking of an INT IN endpoint being the only difference i found. Mark, you should come in #synce more... :-) John ------------------------------------------------------------------------- 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=/ _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
