ok, now i'm confused. to follow along with the patch processing
order, i did a fresh build selecting 2.6 for my WL500GP (which,
underneath, uses 2.6.25.10) and saved the output from "make V=99" so i
could follow the steps.
what i noticed was that 2.6.26 content was being pulled in -- the
2.6.26 tarball was being untarred for (apparently) the headers, then
the directory target/linux/generic-2.6/patches-2.6.26 was being
applied, and so on.
i don't understand this -- why is a build that uses the 2.6.25.10
kernel hauling in 2.6.26 content for *anything*?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
_______________________________________________
openwrt-users mailing list
[email protected]
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
