Skip to content
  1. Jun 25, 2010
  2. Jun 24, 2010
  3. Jun 23, 2010
  4. Jun 22, 2010
    • Peter Korsgaard's avatar
      Merge branch 'linux-cleanup' of git://git.busybox.net/~tpetazzoni/git/buildroot · f3050b0b
      Peter Korsgaard authored
      Conflicts:
      	target/Makefile.in
      f3050b0b
    • Thomas Petazzoni's avatar
      Remove now unused Config.in for kernel selection · 7b7b4260
      Thomas Petazzoni authored
      
      
      It's now linux/Config.in that allows to configure the kernel
      configuration/compilation.
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      7b7b4260
    • Thomas Petazzoni's avatar
      linux: add support for initramfs · f507921d
      Thomas Petazzoni authored
      
      
      In Buildroot, the kernel is built and installed *before* the root
      filesystems are built. This allows the root filesystem to correctly
      contain the kernel modules that have been installed.
      
      However, in the initramfs case, the root filesystem is part of the
      kernel. Therefore, the kernel should be built *after* the root
      filesystem (which, in the initramfs case simply builds a text file
      listing all files/directories/devices/symlinks that should be part of
      the initramfs). However, this isn't possible as the initramfs text
      file would lack all kernel modules.
      
      So, the solution choosen here is to keep the normal order: kernel is
      built before the root filesystem is generated, and to add a little
      quirk to retrigger a kernel compilation after the root filesystem
      generation.
      
      To do so, we add a ROOTFS_$(FSTYPE)_POST_TARGETS variable to the
      fs/common.mk infrastructure. This allows individual filesystems to set
      a target name that we should depend on *after* generating the root
      filesystem itself (contrary to normal ROOTFS_$(FSTYPE)_DEPENDENCIES,
      on which we depend *before* generating the root filesystem).
      
      The initramfs code in fs/initramfs/initramfs.mk uses this to add a
      dependency on 'linux26-rebuild-with-initramfs'.
      
      In linux/linux.mk, we do various things :
      
       * If BR2_TARGET_ROOTFS_INITRAMFS is enabled (i.e if initramfs is
         enabled as a root filesystem type), then we create an empty
         rootfs.initramfs file (remember that at this point, the root
         filesystem hasn't been generated) and we adjust the kernel
         configuration to include an initramfs. Of course, in the initial
         kernel build, this initramfs will be empty.
      
       * In the linux26-rebuild-with-initramfs target, we retrigger a
         compilation of the kernel image, after removing the initramfs in
         the kernel sources to make sure it gets properly rebuilt (we've
         experienced cases were modifying the rootfs.initramfs file wouldn't
         retrigger the generation of the initramfs at the kernel level).
      
      This is fairly quirky, but initramfs really is a special case, so in
      one way or another, we need a little quirk to solve its specialness.
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      f507921d
    • Thomas Petazzoni's avatar
      linux: add support for linux26-{menuconfig,xconfig,gconfig} targets · 4944e8c8
      Thomas Petazzoni authored
      
      
      These targets allow the user to customize the configuration of the
      Linux kernel. After changing the kernel configuration, the next time
      the user runs "make", the kernel is rebuilt to take into account the
      new configuration (not rebuilt from scratch).
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      4944e8c8
    • Thomas Petazzoni's avatar
      linux: adjust kernel config according to the Buildroot configuration · 100c09a5
      Thomas Petazzoni authored
      
      
      We only adjust the configuration or ARM EABI and IPv6. The (more
      complicated) initramfs case is handled in a separate commit. The user
      is expected to take care of all other configuration details (like
      having Netfilter enabled to make iptables work, etc.)
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      100c09a5
    • Thomas Petazzoni's avatar
      Add generic functions to enable/set/disable options in kconfig files · 08023707
      Thomas Petazzoni authored
      
      
      The KCONFIG_ENABLE_OPT, KCONFIG_SET_OPT and KCONFIG_DISABLE_OPT are
      new make functions to respectively enable, set and disable options in
      Kconfig-like files (as used by the kernel, uClibc or Busybox).
      
      They can be used as follows :
      
       $(call KCONFIG_ENABLE_OPT,CONFIG_FOOBAR,/path/to/.config)
       $(call KCONFIG_SET_OPT,CONFIG_BARFOO,foobar,/path/to/.config)
       $(call KCONFIG_DISABLE_OPT,CONFIG_FARBOO,/path/to/.config)
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
      08023707
Loading