| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Make the menu system for configuration more intuitive.
First choose operating system, then hardware, starting with architecture.
Then choose either generic or a sample system. When choosing a sample be more strict
in case of MMU or Endianess selection, so a misconfiguration isn't possible.
Furthermore put a new top level menu for C library configuration and
add Binary format, Instruction set, version selection, float type and
any C library specific options.
Refactor the duplicate definition of Qemu system versatile and Synopsys NSIM.
|
|
|
|
https://github.com/insane-adding-machines/frosted
Rework our architecture selection and os dependent logic a little
bit to be cleaner. As only arm is supported, we only modify
arm systems to comply with new changeset.
|
|
|
|
|
|
|
|
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 don't need this, as ARCH is implicit through the directory.
All lower case symbols should be removed now.
|
|
With this commit I broke Kodi support for cubox-i:
4f93b213f2d3393fbb0b7ca200988f475e6cef83
I found following info regarding VFP and NEON:
http://community.arm.com/groups/tools/blog/2013/04/15/arm-cortex-a-processors-and-gcc-command-lines
Try to implement with this table in mind.
|
|
|
|
NEON is only an extension not the FPU hardware.
So handle this in a better way.
Remove the lower case symbols.
|
|
|
|
|
|
Use one place and not hard coded for each device.
There exist use cases where on a specific device
like raspberry pi, not the default 115200 baud rate
is used.
|
|
|
