We don't need Config.in and Makefile in target/device: defconfig files
are sufficient to describe the specificities of a board (architecture,
compilation flags, bootloader and kernel details, etc.).
However, a placeholder such as target/device will be kept in order to
host things such as kernel configuration files or various
board-specific patches.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Otherwise u-boot tools / kernel modules are only added to target AFTER
the filesystems are built.
Long term u-boot/kernel stuff should get splitted from target/device,
but this is the safest solution for now.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
In order to avoid code duplication between the different filesystem
generation makefile, we introduce a ROOTFS_TARGET macro. Documentation
for this macro is contained in the patch.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
all the different COPYTOs spread out all over
Buildroot.
Generate COPY_FILE subroutine which can be used
to copy a file.
$(COPY_FILE , file, directory, filename)
This will copy to binary dir and to the selected
copy dir if set in new config (intended to replace
all old COPYTO configs)
This is overridden by BUILDROOT_COPYTO,
if set into the environment.
Add linux-2.6.22.1-008-atmel-gpio_mouse-setup-for-atstk1000-board.patch
Move AT91 kernel patches to target/device/Atmel/arch-arm
Change name from "target/device/Atmel/Linux" to "target/device/Atmel/linux"
"kernel-headers" will apply all patches in $(LINUX26_KERNEL_PATCH_DIR)
if this is available.
Define LINUX26_KERNEL_PATCH_DIR in target/device/Atmel/Makefile.in
as above "arch-arm/kernel-patches-..." if an AT91 or
as above "arch-avr32/kernel-patches-..." if an AVR32 target is selected
Test build done for arm,avr32 and x86
