1. 18 2月, 2007 1 次提交
  2. 14 2月, 2007 1 次提交
  3. 22 9月, 2006 1 次提交
    • V
      POWERPC: Add support for the mpc8560 eval board · 902f392d
      Vitaly Bordug 提交于
      This makes the 8560 evaluation board fully supported under arch/powerpc,
      as the first board with CPM2 SoC peripherals. The brand new devicetree
      nodes are introduced (intending to be a subset of the QuiccEngine-equipped
      models, with dts sources placed into the kernel according to the new convention.
      
      Assuming all the preceding stuff applied (PAL+fs_enet related+ CPM_UART
      update), the both TSEC eth ,FCC Eths, and both SCC UARTs are
      working. The relevant drivers are still capable to drive users in ppc,
      which was verified with 8272ADS (SCC uart+FCC eth).
      
      This is also verified on mpc8540 and actually make it work (PCI stuff
      working as well)
      Signed-off-by: NVitaly Bordug <vbordug@ru.mvista.com>
      902f392d
  4. 23 8月, 2006 1 次提交
  5. 05 4月, 2006 1 次提交
  6. 28 3月, 2006 1 次提交
  7. 20 1月, 2006 1 次提交
  8. 26 9月, 2005 1 次提交
    • P
      powerpc: Merge enough to start building in arch/powerpc. · 14cf11af
      Paul Mackerras 提交于
      This creates the directory structure under arch/powerpc and a bunch
      of Kconfig files.  It does a first-cut merge of arch/powerpc/mm,
      arch/powerpc/lib and arch/powerpc/platforms/powermac.  This is enough
      to build a 32-bit powermac kernel with ARCH=powerpc.
      
      For now we are getting some unmerged files from arch/ppc/kernel and
      arch/ppc/syslib, or arch/ppc64/kernel.  This makes some minor changes
      to files in those directories and files outside arch/powerpc.
      
      The boot directory is still not merged.  That's going to be interesting.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      14cf11af
  9. 22 6月, 2005 1 次提交
  10. 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