On Wed, 2008-07-23 at 01:34 +0200, Adam Williamson wrote: > On Fri, 2008-07-18 at 21:45 +0100, Mark Ellis wrote: > > > Ok, whoa :) > > > > I was all ready to start a 'kernel status' thread, and the train went > > without me. Don't get me wrong, this is good, but is there anything else > > we want to submit to the kernel guys ? Considering how long it took to > > get to the stage we're at, it's worth thinking it through first. > > > > I intended to have a good look through usb-rndis-lite and compare it to > > the latest kernel before we had this discussion, but hey. > > > > To my knowledge, and the quick browse I had, we don't have anything in > > usbnet and cdc_ether that needs to be submitted. > > > > In rndis_host, obviously there is the subject of this thread, but has > > the Samsung timeout patch been submitted? Anyone know of anything else ? > > OK, so here's the status now as far as I know: > > The tethering patch has been committed today by David Brownell. So the > two major reasons for rndis-lite's existence are now no longer valid: > kernel.org git now has support for WM5 and WM6 devices, and for > tethering. >
Hurrah ! > As I understand it, any remaining differences between the upstream code > and rndis-lite are now essentially details. I guess it would be feasible > to audit the remaining differences and submit any changes that are > actually useful upstream, with a view to killing usb-rndis-lite > permanently - would that be possible? David Brownell (upstream) is > explicitly interested in any remaining differences between the two: he'd > like to see rndis-lite go away through anything it does better being > merged upstream. > I'm not kernel'ly enough to spot subtle improvements. I did notice that the timeout patch got included in a different form, which is good. I guess usb-rndis-lite will still be around until all the common distros are using later kernels, but at least we're on the right track. > 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
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- 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
