View Single Post
Old 06-04-2012, 01:53 PM   #22
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by BusterBrown View Post
Wonder about this line in Printenv: bootargs_base=console=ttymxc0,115200 mem=256M panic=10
That one is the kernel command line.

Not sure what the "panic=10" kernel command line option is, would have to look that one up in the kernel_source/Documentation tree.
Everything else on that line looks "as expected" (and the kernel is being told to run /dev/console on the same hardware you are now using, at the same speed).

Note: The options on that line which are __not__ consumed by the kernel, are passed onto the next stage of initialization (often to the initramfs or init or whatever is next).
So if you don't find that "panic= " option in the kernel documentation, then it is something for later in the process.

If it helps to read those strings ...
u-boot runs a small version of Busybox ash.
Which is why some look like shell scripting - they are.

Last edited by knc1; 06-04-2012 at 01:57 PM.
knc1 is offline   Reply With Quote