1. 08 12月, 2006 2 次提交
  2. 29 10月, 2006 1 次提交
  3. 28 9月, 2006 5 次提交
  4. 25 9月, 2006 2 次提交
  5. 28 8月, 2006 1 次提交
  6. 29 6月, 2006 1 次提交
  7. 19 6月, 2006 1 次提交
  8. 18 6月, 2006 1 次提交
  9. 09 6月, 2006 1 次提交
  10. 26 4月, 2006 1 次提交
  11. 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
  12. 27 3月, 2006 2 次提交
  13. 22 3月, 2006 1 次提交
  14. 06 3月, 2006 1 次提交
  15. 15 1月, 2006 1 次提交
  16. 10 1月, 2006 1 次提交
  17. 09 1月, 2006 1 次提交
  18. 04 1月, 2006 1 次提交
  19. 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
  20. 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
  21. 03 11月, 2005 1 次提交
  22. 31 10月, 2005 1 次提交
  23. 30 10月, 2005 1 次提交
    • N
      [ARM] 3061/1: cleanup the XIP link address mess · 37d07b72
      Nicolas Pitre 提交于
      Patch from Nicolas Pitre
      
      Since vmlinux.lds.S is preprocessed, we can use the defines already
      present in asm/memory.h (allowed by patch #3060) for the XIP kernel link
      address instead of relying on a duplicated Makefile hardcoded value, and
      also get rid of its dependency on awk to handle it at the same time.
      
      While at it let's clean XIP stuff even further and make things clearer
      in head.S with a nice code reduction.
      Signed-off-by: NNicolas Pitre <nico@cam.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      37d07b72
  24. 13 10月, 2005 1 次提交
  25. 27 9月, 2005 1 次提交
    • A
      [PATCH] missing dependency on arm O= builds · 0b155694
      Al Viro 提交于
      	arm maketools needs include/asm-arm in place in the build tree.
      On normal builds it's always there, of course, but on O= it's created
      (by generic code) too late - when we get to asm-offset.h.
      
      	We used to get away with that by accident - creation of
      include/asm-arm/arch symlink creates include/asm-arm and it happened
      to go before maketools.  However, we did not have such dependency,
      so that luck didn't last - now maketools is picked first and we are screwed.
      
      	Both the symlink and maketools are prerequisites of the same
      target (archprepare).  This fix is obvious - make the latter explicitly
      depend on the former and be done with that.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      0b155694
  26. 12 9月, 2005 1 次提交
    • S
      kbuild: rename prepare to archprepare to fix dependency chain · 5bb78269
      Sam Ravnborg 提交于
      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:
      
      prepare
        |
        +--> 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: NSam Ravnborg <sam@ravnborg.org>
      5bb78269
  27. 10 9月, 2005 1 次提交
  28. 11 7月, 2005 1 次提交
  29. 01 7月, 2005 1 次提交
  30. 21 6月, 2005 1 次提交
  31. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4