On 11/27/13 13:27, Wookey wrote:
+++ Christopher Covington [2013-11-27 11:17 -0500]:
Hi Wookey,
There is a wiki page somewhere for wrapping your own kernel
Wow. Curiosity has gotten the best of me. (new to the list).
I didn't understand a lot of those words, but it really doesn't sound
easier than 'a little shell script that lets me change the command line
in a working .axf kernel'. Turns out said shell script was actually
written wearing a linaro hat so I'll stick it somewhere and add a wiki page.
Wookey
Hi Wookey, remember me? (hint: anakin).....
So, being clueless to Linaro (but good intentions) is not the simple
method to set up a tool chain for either native or cross compiling
depending whatever is needed, kernel, gcc, tools, libraries, etc etc?
With this approach compiling (or fixing code) is a similar effort,
one piece of software at a time. The methodology of booting, from
bootloaders or with a custom boostrap, processor specific, should
be straightforward and all supported.
Is linaro trying to be one of those (useless) commercial embedded
system, where any really neat or useful code is a bolt_on with
little or no documentation on how to build the desired code from
sources?
Why all the gymnastics on images and such; why use what others have
packaged up, in lieu of just compiling the code, kernel or otherwise?
Once that is done, packaging for a particular distro should be
straightforward, if not trivial; or do I "not get the focus of linaro"?
To me, "embedded" means from sources up.....
sincerely,
(James)
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
