I meant, having an option to add anything by just creating ./files/linux-2.6/.config looks a much more flexible approach than just adding another option to the Config.in.
Ideally the makefiles would search for the custom kernel config in ./files/linux/.config ./files/linux-2.6/.config ./files/linux-2.6.26/.config sequentially ----- Original Message ---- > From: Stanislav Sinyagin <[EMAIL PROTECTED]> > To: openwrt-devel@lists.openwrt.org > Sent: Saturday, October 18, 2008 2:09:11 AM > Subject: [OpenWrt-Devel] setting kernel config parameters from ./files/ > > Is there any reference document explaining the structure > of ./files/ directory? For example, include/kernel.mk uses it > to copy some custom modules into the target's lib/modules/$(LINUX_VERSION)/ > > What I'd like to have is a consistent, file-based way to influence > the kernel config options, so that they are not overridden by > the next "make menuconfig". > > In the short term, I want to build a kernel which would have > CONFIG_CMDLINE pointing the root to the USB stick -- basically it's > what bifferos is doing in his squidge distribution. But I want to make it > possible in a way that is consistent with the OpenWRT mainline. > > Another approach would be to add a menu option for CONFIG_CMDLINE into > the OpenWRT's menuconfig script. > > It's not a problem for me to produce a patch for the makefiles, but > I'd like to hear your opinions first. > > thanks, > stan > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
