<div dir="ltr">Thanks Piyush,<div><br></div><div style>I know about the uboot saved parameters. The whole point is that I do not want to touch the by the factory flashed uboot. There are now three CONFIG_CMDLINE options</div>
<div style>1) CONFIG_CMDLINE_BOOTLOADER == Always use the ones passed by the bootloader</div><div style>2 CONFIG_CMDLINE_FORCE == Always use the under CMDLINE defined parameters, ignore the ones passed by the bootloader</div>
<div style>3) CONFIG_EXTEND == Insert parameters and APPEND the ones passed by the bootloader. This is designed such, that you can define missing parameters not defined by the bootloader.</div><div style><br></div><div style>
With the latter, if you define a parameter which is also passed by the bootloader, the by CMDLINE configured one wil be overwritten by the one passed from the bootloader. This is simply because the function to fill for instance the rootfstype parameter is called twice.</div>
<div style><br></div><div style>What I am basically are looking for is a fourth config option, CONFIG_CMDLINE_OVERRIDE, where the by the bootloader passed parameters are being appended by the ones defined in the CMDLINE. It is basically the EXTEND, but then the other way around. It still EXTENDS the ones not defined by the bootloader, but if you define a parameter in the kernel which is also set by the CMDLINE the ones from the bootloader are overwritten by the ones defined in the kernel.</div>
<div style><br></div><div style>At this moment, a quick hack has been applied to set a boolean for the rootfstype one;</div><div style><a href="https://github.com/j1nx/buildroot-linux-kernel-m3/commit/52476f9f911ee9c08acda0976331aa5465ff16a7">https://github.com/j1nx/buildroot-linux-kernel-m3/commit/52476f9f911ee9c08acda0976331aa5465ff16a7</a><br>
</div><div style>But a fourth CONFIG parameter will solve the same issue for any other possible parameters. The thing is; I can't believe I am the only one that wants to override uboot parameters. It might be already out there...</div>
<div style><br></div><div style>Cheers</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 3:32 AM, Piyush Verma <span dir="ltr"><<a href="mailto:piyush.pv@gmail.com" target="_blank">piyush.pv@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">While booting we can stop at uboot prompt.<br><br>there we can see all environment variable with printenv.<br>we can change it by setenv. don't forget to save it by saveenv after changing environment variable.<br>
<br>bootargs is the environment variable where we can pass all rootfs details.<br>
<br>Does it solve ur issue ?<br><br><div class="gmail_quote"><div><div class="h5">On Wed, Feb 20, 2013 at 4:01 AM, Peter Steenbergen <span dir="ltr"><<a href="mailto:p.steenbergen@j1nx.nl" target="_blank">p.steenbergen@j1nx.nl</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">I am running into an issue with my Amlogic XBMC development. Before I go out searching the dark secrets of the linux kernel, I thought why not ask you guys first.<div>
<br></div><div>There is this patch;</div>
<div><a href="http://lists.infradead.org/pipermail/linux-arm-kernel/2011-April/047506.html" target="_blank">http://lists.infradead.org/pipermail/linux-arm-kernel/2011-April/047506.html</a><br></div><div>Which is used often. It adds the CONFIG_CMDLINE_EXTEND to the possible CMDLINE options. It is designed to prepend the cmdline parameters in case there are missing values. The passed parameters by uboot are then appended to the ones from CONFIG_CMDLINE.</div>
<div><br></div><div>This all works fine if you indeed are missing parameters, but what if i want to overwrite/override an already by uboot passed parameter? (like root= and rootfstype=)</div><div><br></div>
<div>I don't want to FORCE everything, because I then have to take over the complete line as passed by uboot. If I do that I will loose the parameters set by variables within uboot (MAC)</div><div><br></div>
<div>If I set them in CMDLINE, then the ones passed from uboot are appended and overriding the ones from CMDLINE.</div><div><br></div><div>I also do not want to change uboot as that is still kind of tricky on the Amlogic boxes.</div>
<div><br></div><div>Do anyone of you guys have some tips and/or directions?</div><div><br></div><div>thanks</div></div>
<br></div></div>_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br>
<br clear="all"><br>-- <br>Thanks & Regards<br><br>Piyush Verma<br><br>
</font></span><br>_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br></blockquote></div><br></div>