1. 27 7月, 2011 1 次提交
  2. 18 11月, 2009 1 次提交
  3. 09 10月, 2009 1 次提交
  4. 09 7月, 2008 1 次提交
    • G
      ibm_newemac: Parameterize EMAC Multicast Match Handling · 05781ccd
      Grant Erickson 提交于
      Various instances of the EMAC core have varying: 1) number of address
      match slots, 2) width of the registers for handling address match slots,
      3) number of registers for handling address match slots and 4) base
      offset for those registers.
      
      As the driver stands today, it assumes that all EMACs have 4 IAHT and
      GAHT 32-bit registers, starting at offset 0x30 from the register base,
      with only 16-bits of each used for a total of 64 match slots.
      
      The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
      core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
      from the register base, with ALL 32-bits of each used for a total of
      256 match slots.
      
      This adds a new compatible device tree entry "emac4sync" and a new,
      related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
      and inlines which supply the appropriate parameterized value based on
      the presence or absence of the EMAC4SYNC feature.
      
      The code has further been reworked where appropriate to use those macros
      and inlines.
      
      In addition, the register size passed to ioremap is now taken from the
      device tree:
      
      	c4 for EMAC4SYNC cores
      	74 for EMAC4 cores
      	70 for EMAC cores
      
      rather than sizeof (emac_regs).
      
      Finally, the device trees have been updated with the appropriate compatible
      entries and resource sizes.
      
      This has been tested on an AMCC Haleakala board such that: 1) inbound
      ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
      and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
      'haleakala.local' to those same systems in the '.local' domain via MDNS
      now work.
      Signed-off-by: NGrant Erickson <gerickson@nuovations.com>
      Acked-by: NJeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      05781ccd
  5. 08 12月, 2007 1 次提交
  6. 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
  7. 01 7月, 2006 1 次提交
  8. 09 1月, 2006 1 次提交
  9. 30 10月, 2005 2 次提交
  10. 29 10月, 2005 1 次提交
    • E
      [PATCH] New PowerPC 4xx on-chip ethernet controller driver · 37448f7d
      Eugene Surovegin 提交于
      This patch replaces current PowerPC 4xx EMAC driver with
      new, re-written from the scratch version. This patch is quite big
      (~234K) because there is virtualy 0% of common code between old and
      new version.
      
      New driver uses NAPI, it solves stability problems under heavy packet
      load and low memory, corrects chip register access and fixes numerous
      small bugs I don't even remember now.
      
      This patch has been tested on all supported in 2.6 PPC 4xx boards.
      It's been used in production for almost a year now on custom
      4xx hardware. PPC32 specific parts are already upstream.
      
      Patch was acked by the current EMAC driver maintainer (Matt Porter). I
      will be maintaining this new version.
      Signed-off-by: NEugene Surovegin <ebs@ebshome.net>
      --
      
       Kconfig                   |   72
       ibm_emac/Makefile         |   13
       ibm_emac/ibm_emac.h       |  418 +++--
       ibm_emac/ibm_emac_core.c  | 3414 ++++++++++++++++++++++++----------------------
       ibm_emac/ibm_emac_core.h  |  313 ++--
       ibm_emac/ibm_emac_debug.c |  377 ++---
       ibm_emac/ibm_emac_debug.h |   63
       ibm_emac/ibm_emac_mal.c   |  674 +++++----
       ibm_emac/ibm_emac_mal.h   |  336 +++-
       ibm_emac/ibm_emac_phy.c   |  335 ++--
       ibm_emac/ibm_emac_phy.h   |  105 -
       ibm_emac/ibm_emac_rgmii.c |  201 ++
       ibm_emac/ibm_emac_rgmii.h |   68
       ibm_emac/ibm_emac_tah.c   |  111 +
       ibm_emac/ibm_emac_tah.h   |   96 -
       ibm_emac/ibm_emac_zmii.c  |  255 +++
       ibm_emac/ibm_emac_zmii.h  |  114 -
       17 files changed, 4114 insertions(+), 2851 deletions(-)
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      37448f7d
  11. 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