1. 02 Oct, 2018 1 commit
    • Rob Herring's avatar
      kbuild: consolidate Devicetree dtb build rules · 37c8a5fa
      Rob Herring authored
      There is nothing arch specific about building dtb files other than their
      location under /arch/*/boot/dts/. Keeping each arch aligned is a pain.
      The dependencies and supported targets are all slightly different.
      Also, a cross-compiler for each arch is needed, but really the host
      compiler preprocessor is perfectly fine for building dtbs. Move the
      build rules to a common location and remove the arch specific ones. This
      is done in a single step to avoid warnings about overriding rules.
      The build dependencies had been a mixture of 'scripts' and/or 'prepare'.
      These pull in several dependencies some of which need a target compiler
      (specifically devicetable-offsets.h) and aren't needed to build dtbs.
      All that is really needed is dtc, so adjust the dependencies to only be
      This change enables support 'dtbs_install' on some arches which were
      missing the target.
      Acked-by: default avatarWill Deacon <will.deacon@arm.com>
      Acked-by: default avatarPaul Burton <paul.burton@mips.com>
      Acked-by: default avatarLey Foon Tan <ley.foon.tan@intel.com>
      Acked-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Michal Marek <michal.lkml@markovi.net>
      Cc: Vineet Gupta <vgupta@synopsys.com>
      Cc: Russell King <linux@armlinux.org.uk>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: Michal Simek <monstr@monstr.eu>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: James Hogan <jhogan@kernel.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Michael Ellerman <mpe@ellerman.id.au>
      Cc: Chris Zankel <chris@zankel.net>
      Cc: Max Filippov <jcmvbkbc@gmail.com>
      Cc: linux-kbuild@vger.kernel.org
      Cc: linux-snps-arc@lists.infradead.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: uclinux-h8-devel@lists.sourceforge.jp
      Cc: linux-mips@linux-mips.org
      Cc: nios2-dev@lists.rocketboards.org
      Cc: linuxppc-dev@lists.ozlabs.org
      Cc: linux-xtensa@linux-xtensa.org
      Signed-off-by: Rob Herring's avatarRob Herring <robh@kernel.org>
  2. 12 Sep, 2018 1 commit
  3. 23 Aug, 2018 1 commit
  4. 10 Dec, 2017 2 commits
    • Max Filippov's avatar
      xtensa: build kernel with text-section-literals · f8f02ca7
      Max Filippov authored
      vmlinux.lds.S doesn't do anything special with literals, so instead of
      keeping them separate put them into the corresponding text sections.
      Drop explicit .literal sections from the vmlinux.lds.S, use standard
      section macros. Mark literal pool locations in the assembly sources.
      Unfortunately assembler doesn't put literals into .init sections and
      external libgcc may still have .literal sections, so sed transformation
      to the linker script is still needed.
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
    • Max Filippov's avatar
      xtensa: add -mno-serialize-volatile to CFLAGS · 7bf5234d
      Max Filippov authored
      By default xtensa gcc inserts memw for all volatile object accesses.
      This is too pessimistic for the kernel: there should be no "normal"
      volatile objects, and all special objects, like MMIO or objects shared
      between CPUs should have explicit barriers.
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
  5. 01 Mar, 2017 1 commit
    • Max Filippov's avatar
      xtensa: clean up bootable image build targets · 9a736fcb
      Max Filippov authored
      Currently xtensa uses 'zImage' as a synonym of 'all', but in fact xtensa
      supports three targets: 'Image' (ELF image with reset vector), 'zImage'
      (compressed redboot image) and 'uImage' (U-Boot image).
      Provide separate 'Image', 'zImage' and 'uImage' make targets that only
      build corresponding image type. Make 'all' build all images appropriate
      for a platform.
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
  6. 11 Mar, 2016 1 commit
  7. 27 Oct, 2015 1 commit
    • Rob Herring's avatar
      xtensa: enable building of all dtbs · 99085704
      Rob Herring authored
      Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
      are not really dependent on a platform being enabled or any other kernel
      config, so for testing coverage it is convenient to build all of the dtbs.
      This builds all dts files in the tree, not just targets listed.
      Signed-off-by: Rob Herring's avatarRob Herring <robh@kernel.org>
      Cc: Chris Zankel <chris@zankel.net>
      Cc: Max Filippov <jcmvbkbc@gmail.com>
      Cc: linux-xtensa@linux-xtensa.org
  8. 21 Oct, 2014 1 commit
    • Daniel Glöckner's avatar
      xtensa: remove s6000 variant and s6105 platform · 4006e565
      Daniel Glöckner authored
      The Stretch s6000 family support has been merged into mainline 5 years
      ago. There appear to be no users of this code since nobody complained
      that there is a merge error preventing compilation.
      Apart from the s6105 IP camera reference design there are no s6000 devices
      known to ever have run Linux and as the chips are out of production there
      probably never will be. The successor s7000 no longer uses an Xtensa core
      for the OS.
      Let's remove the code until someone is found who actually needs it.
      Signed-off-by: default avatarDaniel Glöckner <dg@emlix.com>
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
  9. 14 Aug, 2014 1 commit
    • Max Filippov's avatar
      xtensa: simplify addition of new core variants · 420ae951
      Max Filippov authored
      Instead of adding new Kconfig options and Makefile rules for each new
      core variant provide XTENSA_VARIANT_CUSTOM variant and record variant
      name in the XTENSA_VARIANT_NAME variable. Adding new core variant now
      means providing directory structure under arch/xtensa/variant and
      specifying correct name in kernel configuration.
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
  10. 06 Sep, 2013 1 commit
  11. 24 Feb, 2013 3 commits
  12. 19 Dec, 2012 6 commits
  13. 04 Oct, 2012 1 commit
  14. 03 Oct, 2012 2 commits
  15. 20 Jun, 2012 1 commit
  16. 02 May, 2010 1 commit
    • Chris Zankel's avatar
      xtensa: Add -mforce-no-pic option is supported · cf1c0aaf
      Chris Zankel authored
      GCC is configured to always compile with PIC enabled for the Xtensa
      architecture. This fails when nfsroot is enabled as the code uses a
      non-conformant segment that mismatches in permissione with a read-only
      A patch has been submitted to GCC to add the machine-option 'force-no-pic'
      that disables PIC.
      Signed-off-by: default avatarChris Zankel <chris@zankel.net>
  17. 03 Apr, 2009 4 commits
  18. 06 Nov, 2008 1 commit
  19. 21 Oct, 2008 1 commit
  20. 14 Feb, 2008 1 commit
  21. 14 Oct, 2007 1 commit
    • Sam Ravnborg's avatar
      kbuild: enable 'make CFLAGS=...' to add additional options to CC · a0f97e06
      Sam Ravnborg authored
      The variable CFLAGS is a wellknown variable and the usage by
      kbuild may result in unexpected behaviour.
      On top of that several people over time has asked for a way to
      pass in additional flags to gcc.
      This patch replace use of CFLAGS with KBUILD_CFLAGS all over the
      tree and enabling one to use:
      make CFLAGS=...
      to specify additional gcc commandline options.
      One usecase is when trying to find gcc bugs but other
      use cases has been requested too.
      Patch was tested on following architectures:
      alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k
      Test was simple to do a defconfig build, apply the patch and check
      that nothing got rebuild.
      Signed-off-by: Sam Ravnborg's avatarSam Ravnborg <sam@ravnborg.org>
  22. 27 Aug, 2007 1 commit
  23. 10 Dec, 2006 1 commit
  24. 09 Jun, 2006 1 commit
  25. 11 Sep, 2005 1 commit
    • Sam Ravnborg's avatar
      kbuild: rename prepare to archprepare to fix dependency chain · 5bb78269
      Sam Ravnborg authored
      When introducing the generic asm-offsets.h support the dependency
      chain for the prepare targets was changed. All build scripts expecting
      include/asm/asm-offsets.h to be made when using the prepare target would broke.
      With the limited number of prepare targets left in arch Makefiles
      the trivial solution was to introduce a new arch specific target: archprepare
      The dependency chain looks like this now:
        +--> prepare0
               +--> archprepare
      		+--> scripts_basic
                      +--> prepare1
                             +---> prepare2
                                     +--> prepare3
      So prepare 3 is processed before prepare2 etc.
      This guaantees that the asm symlink, version.h, scripts_basic
      are all updated before archprepare is processed.
      prepare0 which build the asm-offsets.h file will need the
      actions performed by archprepare.
      The head target is now named prepare, because users scripts will most
      likely use that target, but prepare-all has been kept for compatibility.
      Updated Documentation/kbuild/makefiles.txt.
      Signed-off-by: Sam Ravnborg's avatarSam Ravnborg <sam@ravnborg.org>
  26. 09 Sep, 2005 1 commit
  27. 30 Jun, 2005 1 commit
  28. 24 Jun, 2005 1 commit