1. 29 3月, 2012 1 次提交
  2. 09 3月, 2009 1 次提交
    • E
      [ARM] pxa: introduce pxa{25x,27x,300,320,930}.h for board usage · 51c62982
      Eric Miao 提交于
      Considering the header mess ATM, it is not always possible to include
      the correct header files within board code. Let's keep this simple:
      
        <mach/pxa25x.h>  - for pxa25x based platforms
        <mach/pxa27x.h>  - for pxa27x based platforms
        <mach/pxa300.h>  - for pxa300 based platforms
        <mach/pxa320.h>  - for pxa320 based platforms
        <mach/pxa930.h>  - for pxa930 based platforms
      
      NOTE:
      
      1. one header one board file, they are not compatible (i.e. they have
         conflicting definitions which won't compile if included together).
      
      2. Unless strictly necessary, the following header files are considered
         to be SoC files use _only_, and is not recommended to be included in
         board code:
      
          <mach/hardware.h>
          <mach/pxa-regs.h>
          <mach/pxa2xx-regs.h>
          <mach/pxa3xx-regs.h>
          <mach/mfp.h>
          <mach/mfp-pxa2xx.h>
          <mach/mfp-pxa25x.h>
          <mach/mfp-pxa27x.h>
          <mach/mfp-pxa3xx.h>
          <mach/mfp-pxa300.h>
          <mach/mfp-pxa320.h>
          <mach/mfp-pxa930.h>
      Signed-off-by: NEric Miao <eric.miao@marvell.com>
      51c62982
  3. 07 8月, 2008 2 次提交
  4. 01 7月, 2006 1 次提交
  5. 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