1. 11 7月, 2007 3 次提交
  2. 09 7月, 2007 1 次提交
  3. 10 5月, 2007 1 次提交
  4. 09 5月, 2007 1 次提交
    • R
      IB/mlx4: Add a driver Mellanox ConnectX InfiniBand adapters · 225c7b1f
      Roland Dreier 提交于
      Add an InfiniBand driver for Mellanox ConnectX adapters.  Because
      these adapters can also be used as ethernet NICs and Fibre Channel 
      HBAs, the driver is split into two modules: 
       
        mlx4_core: Handles low-level things like device initialization and 
          processing firmware commands.  Also controls resource allocation 
          so that the InfiniBand, ethernet and FC functions can share a 
          device without stepping on each other. 
       
        mlx4_ib: Handles InfiniBand-specific things; plugs into the 
          InfiniBand midlayer. 
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      225c7b1f
  5. 28 4月, 2007 1 次提交
    • K
      ucc_geth: migrate ucc_geth to phylib · 728de4c9
      Kim Phillips 提交于
      migrate ucc_geth to use the common phylib code.
      
      There are several side effects from doing this:
      
      o deprecate 'interface' property specification present
        in some old device tree source files in
        favour of a split 'max-speed' and 'interface-type'
        description to appropriately match definitions
        in include/linux/phy.h.  Note that 'interface' property
        is still honoured if max-speed or interface-type
        are not present (backward compatible).
      o compile-time CONFIG_UGETH_HAS_GIGA is eliminated
        in favour of probe time speed derivation logic.
      o adjust_link streamlined to only operate on maccfg2
        and upsmr.r10m, instead of reapplying static initial
        values related to the interface-type.
      o Addition of UEC MDIO of_platform driver requires
        platform code add 'mdio' type to id list
        prior to calling of_platform_bus_probe (separate patch).
      o ucc_struct_init introduced to reduce ucc_geth_startup
        complexity.
      Signed-off-by: NLi Yang <leoli@freescale.com>
      Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      728de4c9
  6. 26 4月, 2007 1 次提交
  7. 08 2月, 2007 1 次提交
  8. 06 2月, 2007 5 次提交
  9. 02 12月, 2006 6 次提交
    • H
      [PATCH] Atmel MACB ethernet driver · 89e5785f
      Haavard Skinnemoen 提交于
      Driver for the Atmel MACB on-chip ethernet module.
      
      Tested on AVR32/AT32AP7000/ATSTK1000. I've heard rumours that it works
      with AT91SAM9260 as well, and it may be possible to share some code with
      the at91_ether driver for AT91RM9200.
      
      Hardware documentation can be found in the AT32AP7000 data sheet,
      which can be downloaded from
      
      http://www.atmel.com/dyn/products/datasheets.asp?family_id=682
      
      Changes since previous version:
        * Probe for PHY ID instead of depending on it being provided through
          platform_data.
        * Grab initial ethernet address from the MACB registers instead
          of depending on platform_data.
        * Set MII/RMII mode correctly.
      
      These changes are mostly about making the driver more compatible with
      the at91 infrastructure.
      Signed-off-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      89e5785f
    • Z
      [PATCH] Add tsi108/9 On Chip Ethernet device driver support · 5e123b84
      Zang Roy-r61911 提交于
      Add tsi108/9 on chip Ethernet controller driver support.
      
      The driver code collects the feedback of previous posting form the mailing
      list and gives the update.
      
      MPC7448HPC2 platform in arch/powerpc uses tsi108 bridge.
      
      The following is a brief description of the Ethernet controller:
      
      The Tsi108/9 Ethernet Controller connects Switch Fabric to two independent
      Gigabit Ethernet ports,E0 and E1.  It uses a single Management interface to
      manage the two physical connection devices (PHYs).  Each Ethernet port has
      its own statistics monitor that tracks and reports key interface
      statistics.  Each port supports a 256-entry hash table for address
      filtering.  In addition, each port is bridged to the Switch Fabric through
      a 2-Kbyte transmit FIFO and a 4-Kbyte Receive FIFO.
      
      Each Ethernet port also has a pair of internal Ethernet DMA channels to
      support the transmit and receive data flows.  The Ethernet DMA channels use
      descriptors set up in memory, the memory map of the device, and access via
      the Switch Fabric.  The Ethernet Controller’s DMA arbiter handles
      arbitration for the Switch Fabric.  The Controller also has a register bus
      interface for register accesses and status monitor control.
      
      The PMD (Physical Media Device) interface operates in MII, GMII, or TBI
      modes.  The MII mode is used for connecting with 10 or 100 Mbit/s PMDs.
      The GMII and TBI modes are used to connect with Gigabit PMDs.  Internal
      data flows to and from the Ethernet Controller through the Switch Fabric.
      Each
      
      Ethernet port uses its transmit and receive DMA channels to manage data
      flows through buffer descriptors that are predefined by the system (the
      descriptors can exist anywhere in the system memory map).  These
      descriptors are data structures that point to buffers filled with data
      ready to transmit over Ethernet, or they point to empty buffers ready to
      receive data from Ethernet.
      Signed-off-by: NAlexandre Bounine <Alexandre.Bounine@tundra.com>
      Signed-off-by: NRoy Zang <tie-fei.zang@freescale.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      5e123b84
    • A
      Add NetXen 1G/10G ethernet driver. · 3d396eb1
      Amit S. Kale 提交于
      Signed-off-by: NAmit S. Kale <amitkale@netxen.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      3d396eb1
    • A
      [PATCH] 8390 fixes - the final chunk (h8300) · 3470cb1d
      Al Viro 提交于
      The rest of 8390 conversions; ifdef cascade in 8390.h is gone now.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      3470cb1d
    • A
      [PATCH] 8390 fixes - m68k oddballs · 8c6270f9
      Al Viro 提交于
      more 8390 conversions - mac8390, zorro8390 and hydra got the same treatment
      as arm etherh; one more case in 8390.h ifdef cascade is gone.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      8c6270f9
    • A
      [PATCH] beginning of 8390 fixes - generic and arm/etherh · 6c3561b0
      Al Viro 提交于
      etherh and a handful of other odd drivers use different macros when building
      8390.c.  Since we generate a single 8390.o and then link with it, in any
      config with both oddball and normal 8390-based driver we will end up with
      breakage in at least one of them.  Solution: take most of 8390.c into
      lib8390.c and have 8390.c, etherh.c and the rest of oddballs #include it.
      Helper macros are taken from 8390.h to whoever includes lib8390.c.  That
      way odd drivers get separate instances of compiled 8390 stuff and stop
      stepping on each other's toes.  8390.h gets cleaned up - we don't have
      the cascade of ifdefs in there and are left with the stuff that can be
      used by any 8390-based driver.  Current problems are exactly because of
      that cascade - we attempt to choose the set of helpers by looking at config
      and that, of course, doesn't work well when we have several sets needed
      by various drivers in our config.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      6c3561b0
  10. 23 9月, 2006 1 次提交
  11. 14 9月, 2006 1 次提交
    • J
      [PATCH] ehea: IBM eHEA Ethernet Device Driver · 7a291083
      Jan-Bernd Themann 提交于
      Hi Jeff,
      
      I fixed the __iomem issue and tested the driver with sparse. Looks good so far.
      Thanks for your effort.
      
      Jan-Bernd Themann
      Signed-off-by: NJan-Bernd Themann <themann@de.ibm.com>
      
       drivers/net/Kconfig             |    9
       drivers/net/Makefile            |    1
       drivers/net/ehea/Makefile       |    6
       drivers/net/ehea/ehea.h         |  447 ++++++
       drivers/net/ehea/ehea_ethtool.c |  294 ++++
       drivers/net/ehea/ehea_hcall.h   |   51
       drivers/net/ehea/ehea_hw.h      |  287 ++++
       drivers/net/ehea/ehea_main.c    | 2654 ++++++++++++++++++++++++++++++++++++++++
       drivers/net/ehea/ehea_phyp.c    |  705 ++++++++++
       drivers/net/ehea/ehea_phyp.h    |  455 ++++++
       drivers/net/ehea/ehea_qmr.c     |  582 ++++++++
       drivers/net/ehea/ehea_qmr.h     |  358 +++++
       12 files changed, 5849 insertions(+)
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      7a291083
  12. 20 8月, 2006 1 次提交
  13. 29 7月, 2006 1 次提交
    • R
      [PATCH] qla3xxx NIC driver · 5a4faa87
      Ron Mercer 提交于
      This is a complementary network driver for our ISP4XXX parts.
      
      There is a concurrent effort underway to get the iSCSI driver (qla4xxx)
      integrated upstream as well.
      
      I have been through several iterations with the linux-netdev list and have had
      much response from Stephen Hemminger.
      
      - Built and tested using kernel 2.6.17-rc4.
      
      - The chip supports two ethernet and two iSCSI functions.
      
      - The functions ql_sem_lock, ql_sem_spinlock, ql_sem_unlock, and
        ql_wait_for_drvr_lock are used to protect resources that are shared across
        the network and iSCSI functions.  This protection is mostly during chip
        initialization and resets, but also include link management.
      
      - The PHY/MII are not exported through ethtool due to the fact that the
        iSCSI function will control the common link at least 50% of the time.
      
      This driver has been through several iterations on the netdev list and we feel
      this driver is ready for inclusion in the upstream kernel.
      
      It has been built and tested on x86 and PPC64 platforms.
      
      Cc: Jeff Garzik <jeff@garzik.org>
      Cc: Stephen Hemminger <shemminger@osdl.org>
      Signed-off-by: NRon Mercer <ron.mercer@qlogic.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      5a4faa87
  14. 20 7月, 2006 1 次提交
  15. 23 6月, 2006 1 次提交
  16. 24 5月, 2006 1 次提交
  17. 21 4月, 2006 1 次提交
  18. 23 3月, 2006 1 次提交
  19. 10 1月, 2006 1 次提交
    • J
      [NET]: Add IFB (Intermediate Functional Block) network device. · 253af423
      Jamal Hadi Salim 提交于
      A new device to do intermidiate functional block in a system shared
      manner.  To use the new functionality, you need to turn on
      qos/classifier actions.
      
      The new functionality can be grouped as:
      
      1) qdiscs/policies that are per device as opposed to system wide.  ifb
      allows for a device which can be redirected to thus providing an
      impression of sharing.
      
      2) Allows for queueing incoming traffic for shaping instead of
      dropping.
      
      Packets are redirected to this device using tc/action mirred redirect
      construct. If they are sent to it by plain routing instead then they
      will merely be dropped and the stats would indicate that.
      Signed-off-by: NJamal Hadi Salim <hadi@cyberus.ca>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      253af423
  20. 19 11月, 2005 2 次提交
    • L
      [PATCH] intel ixp2000 network driver · 15d014d1
      Lennert Buytenhek 提交于
      The way the hardware and firmware work is that there is one shared RX
      queue and IRQ for a number of different network interfaces.  Due to this,
      we would like to process received packets for every interface in the same
      NAPI poll handler, so we need a pseudo-device to schedule polling on.
      
      What the driver currently does is that it always schedules polling for
      the first network interface in the list, and processes packets for every
      interface in the poll handler for that first interface -- however, this
      scheme breaks down if the first network interface happens to not be up,
      since netif_rx_schedule_prep() checks netif_running().
      
      sky2 apparently has the same issue, and Stephen Hemminger suggested a
      way to work around this: create a variant of netif_rx_schedule_prep()
      that does not check netif_running().  I implemented this locally and
      called it netif_rx_schedule_prep_notup(), and it seems to work well,
      but it's something that probably not everyone would be happy with.
      
      The ixp2000 is an ARM CPU with a high-speed network interface in the
      CPU itself (full duplex 4Gb/s or 10Gb/s depending on the IXP model.)
      The CPU package also contains 8 or 16 (again depending on the IXP
      model) 'microengines', which are somewhat primitive but very fast
      and efficient processor cores which can be used to offload various
      things from the main CPU.
      
      This driver makes the high-speed network interface in the CPU visible
      and usable as a regular linux network device.  Currently, it only
      supports the Radisys ENP2611 IXP board, but adding support for other
      board types should be fairly easy.
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      15d014d1
    • A
      [PATCH] Gianfar update and sysfs support · 7f7f5316
      Andy Fleming 提交于
      This seems to have gotten lost, so I'll resend.
      Signed-off-by: NAndy Fleming <afleming@freescale.com>
      
      * Added sysfs support to gianfar for modifying FIFO and stashing parameters
      * Updated driver to support 10 Mbit, full duplex operation
      * Improved comments throughout
      * Cleaned up and optimized offloading code
      * Fixed a bug where rx buffers were being improperly mapped and unmapped
      * (only manifested if cache-coherency was off)
      * Added support for using the eTSEC exact-match MAC registers
      * Bumped the version to 1.3
      * Added support for distinguishing between reduced 100 and 10 Mbit modes
      * Modified default coalescing values to lower latency
      * Added documentation
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      7f7f5316
  21. 09 11月, 2005 1 次提交
    • M
      [PPP]: add PPP MPPE encryption module · b3f9b92a
      Matt Domsch 提交于
      From: Matt Domsch <Matt_Domsch@dell.com>
      
      The patch below implements the Microsoft Point-to-Point Encryption method
      as a PPP compressor/decompressor.  This is necessary for Linux clients and
      servers to interoperate with Microsoft Point-to-Point Tunneling Protocol
      (PPTP) servers (either Microsoft PPTP servers or the poptop project) which
      use MPPE to encrypt data when creating a VPN.
      
      This patch differs from the kernel_ppp_mppe DKMS pacakge at
      pptpclient.sourceforge.net by utilizing the kernel crypto routines rather
      than providing its own SHA1 and arcfour implementations.
      
      Minor changes to ppp_generic.c try to prevent a link from disabling
      compression (in our case, the encryption) after it has started using
      compression (encryption).
      
      Feedback to <pptpclient-devel@lists.sourceforge.net> please.
      Signed-off-by: NMatt Domsch <Matt_Domsch@dell.com>
      Cc: James Cameron <james.cameron@hp.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Signed-off-by: NBrice Goglin <Brice.Goglin@ens-lyon.org>
      Acked-by: NPaul Mackerras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b3f9b92a
  22. 29 10月, 2005 1 次提交
  23. 19 10月, 2005 1 次提交
  24. 28 9月, 2005 1 次提交
  25. 24 9月, 2005 1 次提交
  26. 14 9月, 2005 1 次提交
  27. 07 9月, 2005 1 次提交
  28. 17 8月, 2005 1 次提交
    • S
      [PATCH] sky2: new experimental Marvell Yukon2 driver · cd28ab6a
      Stephen Hemminger 提交于
      New driver for the Marvell Yukon2 Gigabit Ethernet chipset.
      This driver is based on the skge driver, but using the logic
      from the SysKonnect version of the sk98lin driver.
      It should support all the Yukon2 chipsets that are available
      in many current Intel and AMD motherboards.
      
      The driver does support ethtool, tx and rx checksum, and
      tcp segmentation offload.  But it has only been tested for
      a short while and is known to stop receiving under heavy load.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      cd28ab6a