1. 16 10月, 2007 1 次提交
    • S
      kbuild: enable 'make AFLAGS=...' to add additional options to AS · 222d394d
      Sam Ravnborg 提交于
      The variable AFLAGS 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 AFLAGS with KBUILD_AFLAGS all over
      the tree.
      
      Patch was tested on following architectures:
      alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k, s390
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      222d394d
  2. 15 10月, 2007 1 次提交
    • S
      kbuild: enable 'make CFLAGS=...' to add additional options to CC · a0f97e06
      Sam Ravnborg 提交于
      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: NSam Ravnborg <sam@ravnborg.org>
      a0f97e06
  3. 22 7月, 2007 1 次提交
  4. 12 5月, 2007 2 次提交
  5. 09 5月, 2007 1 次提交
  6. 21 2月, 2007 1 次提交
  7. 20 2月, 2007 1 次提交
  8. 18 2月, 2007 1 次提交
  9. 16 2月, 2007 1 次提交
  10. 12 2月, 2007 1 次提交
  11. 08 2月, 2007 1 次提交
  12. 08 12月, 2006 2 次提交
  13. 29 10月, 2006 1 次提交
  14. 28 9月, 2006 5 次提交
  15. 25 9月, 2006 2 次提交
  16. 28 8月, 2006 1 次提交
  17. 29 6月, 2006 1 次提交
  18. 19 6月, 2006 1 次提交
  19. 18 6月, 2006 1 次提交
  20. 09 6月, 2006 1 次提交
  21. 26 4月, 2006 1 次提交
  22. 29 3月, 2006 2 次提交
    • L
      [ARM] 3388/1: ixp23xx: add core ixp23xx support · c4713074
      Lennert Buytenhek 提交于
      Patch from Lennert Buytenhek
      
      This patch adds support for the Intel ixp23xx series of CPUs.  The
      ixp23xx is an XSC3 based CPU with 512K of L2 cache, a 64bit 66MHz PCI
      interface, two DDR RAM interfaces, QDR RAM interfaces, two gigabit
      MACs, two 10/100 MACs, expansion bus, four microengines, a Media and
      Switch Fabric unit almost identical to the one on the ixp2400, two
      xscale (8250ish) UARTs and a bunch of other stuff.
      
      This patch adds the core ixp23xx support code, and support for the
      ADI Engineering Roadrunner, Intel IXDP2351, and IP Fabrics Double
      Espresso platforms.
      Signed-off-by: NDeepak Saxena <dsaxena@plexity.net>
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      c4713074
    • L
      [ARM] 3377/2: add support for intel xsc3 core · 23bdf86a
      Lennert Buytenhek 提交于
      Patch from Lennert Buytenhek
      
      This patch adds support for the new XScale v3 core.  This is an
      ARMv5 ISA core with the following additions:
      
      - L2 cache
      - I/O coherency support (on select chipsets)
      - Low-Locality Reference cache attributes (replaces mini-cache)
      - Supersections (v6 compatible)
      - 36-bit addressing (v6 compatible)
      - Single instruction cache line clean/invalidate
      - LRU cache replacement (vs round-robin)
      
      I attempted to merge the XSC3 support into proc-xscale.S, but XSC3
      cores have separate errata and have to handle things like L2, so it
      is simpler to keep it separate.
      
      L2 cache support is currently a build option because the L2 enable
      bit must be set before we enable the MMU and there is no easy way to
      capture command line parameters at this point.
      
      There are still optimizations that can be done such as using LLR for
      copypage (in theory using the exisiting mini-cache code) but those
      can be addressed down the road.
      Signed-off-by: NDeepak Saxena <dsaxena@plexity.net>
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      23bdf86a
  23. 27 3月, 2006 2 次提交
  24. 22 3月, 2006 1 次提交
  25. 06 3月, 2006 1 次提交
  26. 15 1月, 2006 1 次提交
  27. 10 1月, 2006 1 次提交
  28. 09 1月, 2006 1 次提交
  29. 04 1月, 2006 1 次提交
  30. 10 11月, 2005 1 次提交
    • T
      [ARM] 3145/1: OMAP 3a/5: Add support for omap24xx · 1dbae815
      Tony Lindgren 提交于
      Patch from Tony Lindgren
      
      This patch adds support for omap24xx series of processors.
      The files live in arch/arm/mach-omap2, and share common
      files with omap15xx and omap16xx processors in
      arch/arm/plat-omap.
      
      Omap24xx support was originally added for 2.6.9 by TI.
      This code was then improved and integrated to share common
      code with omap15xx and omap16xx processors by various
      omap developers, such as Paul Mundt, Juha Yrjola, Imre Deak,
      Tony Lindgren, Richard Woodruff, Nishant Menon, Komal Shah
      et al.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      1dbae815
  31. 05 11月, 2005 1 次提交
    • N
      [ARM] 3097/1: change library link ordering · 30c2f90b
      Nicolas Pitre 提交于
      Patch from Nicolas Pitre
      
      We have an optimized sha1 routine (arch/arm/lib/sha1.S) meant to
      override the generic one in lib/sha1.c.
      
      Unfortunately lib/lib.a is listed _before_ arch/arm/lib/lib.a in the
      link argument list and therefore the architecture specific lib functions
      are not picked up before the generic versions.
      
      This patch is a quick fix to change that ordering for ARM.  Here's what
      the kbuild maintainer had to say about it (was also CC'd on lkml):
      
      On Wed, 2 Nov 2005, Sam Ravnborg wrote:
      > This looks like an obvious way to achive correct ordering.
      > We could change it so arch defines always took precedence but
      > the above is so simple that it is not worth the effort.
      Signed-off-by: NNicolas Pitre <nico@cam.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      30c2f90b