summaryrefslogtreecommitdiff
path: root/target/avr32/Makefile
AgeCommit message (Collapse)Author
2023-02-19atmel-ngw100: fix sd card bootWaldemar Brodkorb
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-01-10add basic support for atmel ngw100. no runtime testing yetWaldemar Brodkorb
2014-09-09add toolchain support for avr32Waldemar Brodkorb
2014-01-16good bye avr32, bad toolchain support, hardware is eol and no qemu emulator ↵Waldemar Brodkorb
available
2012-01-15mk/image.mk: improve and simplify initramfs generationPhil Sutter
Using the kernel tools is a lot better than calling cpio ourselfs, as this way we can have it create device nodes for us. So no need to reopen /dev/console and things like that. While here, fix also initramfs compression (untested), as in my experience the kernel drops all symbols regarding compression from it's .config in the first compile phase. Probably one should make the actual compression algorithm configurable (and ideally depending on what the kernel supports for the given architecture). This is a rough hack based on what I'm using in the custom viprinux build file, so something like this is already running somewhere. ;)
2011-10-12add basic support for avr32 -> ngw100Waldemar Brodkorb