Age | Commit message (Collapse) | Author |
|
After the addition of bare metal toolchains the menu system allowed
to create non-valid configurations. I reworked it so we can also
add other operating system support if we wish.
So first you choose your operating system, then your architecture
and endianess, after that your embedded system, emulator or
generic device and then you choose your task you want to run.
Tasks may be toolchain, a new appliance/application or some preconfigured
sets of packages and configurations as kodi, mpd, firefox and more.
The tasks are limited to a plausible choice of hardware and software.
Deduplicate CPU configuration.
You don't wanna compile Kodi for a H8/300 microcontroller ;)
|
|
Some targets do not support compressed kernels or initramfs.
OpenADK combines both, there is no support for mixed setups.
For example Kernel with gzip, initramfs with xz.
Qemu-Metag f.e. can only use uncompressed initramfs.
The kernel could be compressed, but mixed setup isn't
available for now.
|
|
simulator running test-suites with network functions
|
|
We do not need to manually set mini.config file anymore.
Every target system, even Qemu emulating different models get
it its own. Cleaner and simpler to add new targets.
|
|
|
|
|
|
|
|
|
|
|
|
We don't need this, as ARCH is implicit through the directory.
All lower case symbols should be removed now.
|
|
|
|
|
|
Qemu emulates a Coldfire Evaluation board without MMU.
As that is the first non-MMU platform in OpenADK I added
ADK_TARGET_UCLINUX. Mksh can not be used for non-MMU, because
it requires fork() for job control and other things.
We use hush here. non-MMU support in uClibc does not have
shared library support.
Kernel does not start yet. So no runtime testing, but at least
coldfire toolchain can be tested with uClibc-ng.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
|
|
|