| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Cleanup the package directory which is always used as intermediate step
to build in the default some xz compressed archives with all package
data. While reconfiguring the kernel mini.config or custom config
changes to the firmware did not happen always.
Some targets where redundant and the install step tries to compile, too.
Be more quiet with any cpio usage.
|
|
|
|
- cmdline.txt is not required with full device tree capable kernel
- force 270x option for mkknlimg trailer
- we need ext4 filesystem support in the kernel other filesystems are
rarely used at the moment
- ATAGS and CMDLINE_FROM_BOOTLOADER not required with device tree capable kernel
- overlay dtb files are renamed to dtbo suffix
|
|
Signed-off-by: Alexander Brand <tecnologic86@gmail.com>
|
|
Module loading was broken, use stable hashes and
add kernel versions to allow kernel module loading.
Convert kinetis-k70 to use new infrastructure.
|
|
They can be used elsewhere in the code when this kernels
are used or need special handling.
Bug reported by Diez for RPI kernels.
|
|
|
|
|
|
|
|
Greg Ungerer made me aware of this possibility.
Rather hackish implementation, we need to deduplicate later.
Update Linux Kernel to 4.4.19 while there.
Only non-Devicetree system supported right now.
|
|
|
|
|
|
|
|
Instead of trying to recreate patchsets for newer kernels just use
upstream non-official kernel trees.
Working on the patchsets does take to much time.
You can choose between hardware specific github tree and defconfig
or upstream kernel and OpenADK miniconfig.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
coreutils on host
|
|
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.
|
|
|
|
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>
|
|
|
|
CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_SUNXI=y make sense together
Signed-off-by: Martin Thomas <mthomas@hamtam.de>
|
|
|
|
|
|
|
|
Otherwise toolchain only compiling of gcc is failing
while trying to install header files.
|
|
|
|
|
|
|
|
This change is straightforward but in toolchain/kernel-headers/Makefile
which seems to be called before ${BUILD_DIR}/linux symlink exists.
Therefore define LINUX_DIR to the correct value in between inclusion of
vars.mk (through rules.mk) and kernel-vars.mk.
|
|
|
|
The Kernel need a trailer to be recognized as a device-tree
kernel. The overlay dir is called /boot/overlays.
Now my driver works fine.
|
|
userland, fixes DMA problem fro me
|
|
|
|
|
|
|
|
|
|
Use --with-cpu for gcc to have optimized code for
requested ARM cpus.
Add some basic support for cortex-m3.
|
|
|
|
|
|
|
|
|
