On 2012-02-08 9:41 PM, Lukas Macura wrote: > Hi to all, > > please I would want to start some discussion about possibility to have > more states for kernel modules in config. > > Now it is possible to: > > CONFIG_PACKAGE_kmod-dm=n (no support at all) > or > CONFIG_PACKAGE_kmod-dm=y (supported as module, which is automaticaly > installed to root, loaded automaticaly from init) > or > CONFIG_PACKAGE_kmod-dm=m (supported as external package) > > Maybe it would be great to add > CONFIG_PACKAGE_kmod-dm=M or something else to include module directly > INTO kernel. I think adding this to the menuconfig code and the rest of the build system would add way too much configuration bloat for something that's typically only a small corner case, relevant only to few users. I don't think that's a good tradeoff at all.
> Now, it can be made only by hacking or adding some platform. But for x86 > platforms, there can be realy plenty of configurations. > I think, especialy for x86, this could ease complexity of adding new > boards and make buildtree more flexible. > > For example, if we have some board where we need some kind of sata > driver, there is no chance to make openwrt working without make > kernel_config. > But if buildroot knows option to embed module directly into kernel > image, it could be done much more easily. You could use ./scripts/env to store your configuration, then use make kernel_menuconfig CONFIG_TARGET=env, which will store your kernel config changes without touching any files under version control. It will store all of your modifications (and only the actual modifications, not the full config) under ./env/kernel-config - Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
