On Tuesday 09 November 2010, Wolfgang Spraul wrote: > Florian and Greg, > > > > Just a small comment to say that Android is not the only one (but > > > certainly the most visible, and thus easiest to bash on) not making > > > effort to get their stuff in mainline. OpenWRT people are also > > > maintaining their fork of the kernel, without even using git, and not > > > contributing much to mainline (I'm certainly mistaken on that last > > > comment). > > > > You are a bit rude and mistaking at the same time. We did contribute back > > TI AR7, Mikrotik RB532, RDC R-321x, IXP4xx to name a few and a lot of > > various patches on different related projects. > > I'm speaking as a bystander here, but Lars-Peter Clausen took an enormous > effort to get an entire new SoC, Ingenic's XBurst 4740, into mainline > Linux, using the OpenWrt patch system as his development/staging area. > A lot of that work was merged mainline in 2.6.36, some more is coming. > > I think the mainline quality standards are high (nothing wrong with that), > so it's not easy to get stuff up to that level. And there is not exactly > much of a pull force either, if I may say so. > > I have worked on numerous projects, platforms and build systems over > the years. The OpenWrt people and tools are some of the most upstream > oriented and best ways to get upstream I have seen. > > The next big thing I will try to lend a helping hand to will be the > kernel.org inclusion of the Milkymist SoC. > A fairly clean and constantly re-based kernel is here > https://github.com/tmatsuya/linux-2.6 > Linux 2.6.36+ is already booting, now it 'only' needs to go mainline ;-) > http://lists.milkymist.org/pipermail/devel-milkymist.org/2010-October/00097 > 9.html > > Anybody mainline care to pull directly? That would be awesome. Otherwise > my next best bet would be to go to OpenWrt first, hack it into SVN > patches, then go from there. At least OpenWrt cares a lot to produce > buildable and bootable images at any time, that's an excellent way to > go for bigger and better things. > > From the perspective of someone looking from mainline, I can understand > the frustration over not seeing a git repo that one can pull from at Well there is a git repo, from the bottom of the working with SVN page it says:-
If you prefer working with git, it is possible to use: git://nbd.name/openwrt.git (clone of trunk) git://nbd.name/packages.git (clone of packages) but of course it is not just the kernel that is there, and the patches are in a form that is not directly applicable to the upstream kernel. It might be possible to build a system that extracted just the kernel patches and applied them to a vanilla kernel and then they could be offered upstream, but it would be quite a job to manage it in chunks that made sense to the upstream communities and it would have to remember to submit patches to the right places. So this is no small job. David > any time. But from the outside it looks a bit different. Patches are > sometimes forced to live outside mainline for a long long time, years. > And in those years the way OpenWrt is dealing with patches is still a > very effective system to avoid bitrot. > > my 2c, > Wolfgang > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
