On Tue, Jan 20, 2009 at 00:30, Warren Turkal <w...@penguintechs.org> wrote: > 1. What specific kernel version is the 2.6.28 kernel patch set > designed to be applied (2.6.28 or 2.6.28.1)? How do I look this > information up for myself?
That's set in the LINUX_VERSION variable in the target's Makefile (target/linux/brcm47xx/Makefile). Since that's still set to a 2.6.25 series AFAICT, it looks like the 2.6.28 portion is just staged and not yet intended to build. > 2. What is a good workflow for applying part of the series of patches > so that I can make a modification to a specific patch? If you can unravel the spaghetti-soup Makefile mess and figure that out, please let us all know. I've typically just hand-patched until I got where I needed. > I also have a methodology question. Why are their files and patches > instead of only maintaining a list of patches? It is my experience that 'files' are typically original works with no parent file in the target tree, whereas 'patches' are against existing work. No idea why that (or many other like it) decision was made, but it's there. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
