1. 18 10月, 2008 1 次提交
  2. 03 10月, 2008 1 次提交
    • V
      powerpc/44x: Add AMCC Arches eval board support · e00de30a
      Victor Gallardo 提交于
      The Arches Evaluation board is based on the AMCC 460GT SoC chip.
      This board is a dual processor board with each processor providing
      independent resources for Rapid IO, Gigabit Ethernet, and serial
      communications.  Each 460GT has it's own 512MB DDR2 memory, 32MB NOR FLASH,
      UART, EEPROM and temperature sensor, along with a shared debug port.
      The two 460GT's will communicate with each other via shared memory,
      Gigabit Ethernet and x1 PCI-Express.
      Signed-off-by: NVictor Gallardo <vgallardo@amcc.com>
      Signed-off-by: NJosh Boyer <jwboyer@linux.vnet.ibm.com>
      e00de30a
  3. 28 8月, 2008 8 次提交
  4. 04 7月, 2008 1 次提交
  5. 11 6月, 2008 1 次提交
  6. 03 4月, 2008 1 次提交
  7. 26 3月, 2008 3 次提交
  8. 16 2月, 2008 1 次提交
  9. 25 1月, 2008 2 次提交
  10. 24 12月, 2007 7 次提交
  11. 20 10月, 2007 3 次提交
  12. 11 10月, 2007 1 次提交
    • D
      Device tree aware EMAC driver · 1d3bb996
      David Gibson 提交于
      Based on BenH's earlier work, this is a new version of the EMAC driver
      for the built-in ethernet found on PowerPC 4xx embedded CPUs.  The
      same ASIC is also found in the Axon bridge chip.  This new version is
      designed to work in the arch/powerpc tree, using the device tree to
      probe the device, rather than the old and ugly arch/ppc OCP layer.
      
      This driver is designed to sit alongside the old driver (that lies in
      drivers/net/ibm_emac and this one in drivers/net/ibm_newemac).  The
      old driver is left in place to support arch/ppc until arch/ppc itself
      reaches its final demise (not too long now, with luck).
      
      This driver still has a number of things that could do with cleaning
      up, but I think they can be fixed up after merging.  Specifically:
      	- Should be adjusted to properly use the dma mapping API.
      Axon needs this.
      	- Probe logic needs reworking, in conjuction with the general
      probing code for of_platform devices.  The dependencies here between
      EMAC, MAL, ZMII etc. make this complicated.  At present, it usually
      works, because we initialize and register the sub-drivers before the
      EMAC driver itself, and (being in driver code) runs after the devices
      themselves have been instantiated from the device tree.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      1d3bb996
  13. 07 9月, 2007 1 次提交
  14. 20 8月, 2007 1 次提交
  15. 17 5月, 2007 1 次提交
  16. 08 5月, 2007 1 次提交