<br><br>On Monday, 30 March 2015, Adam Lee <<a href="mailto:adam8157@gmail.com">adam8157@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Mar 30, 2015 at 02:05:33PM +0800, Woody Wu wrote:<br>
> Sorry, I did not write a subject.<br>
><br>
> On Monday, 30 March 2015, Woody Wu <<a href="javascript:;" onclick="_e(event, 'cvml', 'narkewoody@gmail.com')">narkewoody@gmail.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I have a kernel already run on production, but I then realized that I need<br>
> to add one or two driver to it. But I hope I can avoid to upgrade the<br>
> kernel image for those already running products, I hope I can only extend<br>
> the kernel by add the driver modules to the root file system. Is that<br>
> possible? The current kernel has already compiled with the loadable modules<br>
> options, but for the drivers that I want now the old config is 'no'.<br>
><br>
> Thanks in advance.<br>
> -woody <br>
><br>
> --<br>
> Sent from Gmail Mobile<br>
><br>
> --<br>
> Sent from Gmail Mobile<br>
<br>
Sure you can, just compile them as "M" then install into your rootfs, or<br>
compile them as external modules.<br>
<br>
ref:<br>
<a href="https://www.kernel.org/doc/Documentation/kbuild/modules.txt" target="_blank">https://www.kernel.org/doc/Documentation/kbuild/modules.txt</a><br>
<br>
--<br>
Adam Lee<br>
<a href="http://adam8157.info" target="_blank">http://adam8157.info</a><br>
</blockquote><div><br></div><div>Thanks and glad to know that. Just be curious, it means, in kernel building, select a driver as M or as EMPTY will put no influence on the resulted kernel image at all, is it right? Previously, I always thought, when I choice a driver as module, I was not only creating a module itself, but also force the kernel create some kind of a stub in it's image. Now it seems my thoughts is wrong.</div><div> </div><br><br>-- <br>Sent from Gmail Mobile<br>