summaryrefslogtreecommitdiff
path: root/target/or1k
AgeCommit message (Collapse)Author
2015-10-24add new symbol for systems with tcp/ip but without netdevice. like arc ↵Waldemar Brodkorb
simulator running test-suites with network functions
2015-10-23or1k: allow to boot linux kernel, fix compression none modeWaldemar Brodkorb
2015-10-23add or1ksim basic filesWaldemar Brodkorb
2015-10-13use MALLOC_STANDARD, MALLOC does not compileWaldemar Brodkorb
2015-10-12add config for uClibc-ng 1.0Waldemar Brodkorb
2015-10-09add ethernet driver support for qemu-system-or32Waldemar Brodkorb
2015-10-09add some basic uClibc or1k supportWaldemar Brodkorb
2015-10-07bump linux kernelsWaldemar Brodkorb
2015-09-15add more symbols for or1k defconfigWaldemar Brodkorb
2015-09-03select or1k cpuWaldemar Brodkorb
2015-09-01or1k: add basic qemu supportWaldemar Brodkorb
Kernel boots, userland not.
2015-08-03rework kernel module infrastructureWaldemar Brodkorb
Instead of maintaining mk/modules.mk which defines compilations of related kernel modules to pack together into a single package, follow an automatic approach: For every kernel module found in the modules installation directory, create a single package. There are a few caveats to cover: === Module Loading Order === Upon bootup, module loading is ordered based on the number-prefixed files in /etc/modules.d/. The correct number was previously managed in mk/modules.mk on a per-collection basis. The new approach is to have levels which modules are to be assigned to. Level 0 contains modules with no dependencies at all. Level 1 contains modules which have only level 0 dependencies, and so on. This information is determined at compile-time by make-module-ipkgs.sh. === Module Installation to Target RootFS === Since module packages are created automatically from the modules the script finds, ADK build system has no knowledge about the connection between what the user has selected in menuconfig and the actual module packages. Therefore the earlier approach to install selected packages into rootfs does not hold anymore. Instead, use wildcards to find all packages in firmware directory prefixed by 'kmod-' and install them all (hopefully doing the right thing). === Kernel Version === KERNEL_VERSION now contains KERNEL_RELEASE already By creating a localversion file, make KERNEL_RELEASE part of the kernel's version number (so KERNEL_VERSION is correct in most situations) Signed-off-by: Phil Sutter <phil@nwl.cc>
2015-07-13add basic toolchain support for or1k arch with musl libcWaldemar Brodkorb