1. 29 1月, 2008 1 次提交
  2. 29 10月, 2007 1 次提交
  3. 23 10月, 2007 2 次提交
    • R
      Remove old lguest bus and drivers. · 0ca49ca9
      Rusty Russell 提交于
      This gets rid of the lguest bus, drivers and DMA mechanism, to make
      way for a generic virtio mechanism.
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      0ca49ca9
    • R
      Net driver using virtio · 296f96fc
      Rusty Russell 提交于
      The network driver uses two virtqueues: one for input packets and one
      for output packets.  This has nice locking properties (ie. we don't do
      any for recv vs send).
      
      TODO:
      	1) Big packets.
      	2) Multi-client devices (maybe separate driver?).
      	3) Resolve freeing of old xmit skbs (Christian Borntraeger)
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Herbert Xu <herbert@gondor.apana.org.au>
      Cc: netdev@vger.kernel.org
      296f96fc
  4. 16 10月, 2007 1 次提交
  5. 11 10月, 2007 9 次提交
  6. 16 9月, 2007 1 次提交
  7. 30 7月, 2007 1 次提交
  8. 25 7月, 2007 1 次提交
  9. 20 7月, 2007 1 次提交
  10. 19 7月, 2007 1 次提交
    • B
      Blackfin ethernet driver: on chip ethernet MAC controller driver · e190d6b1
      Bryan Wu 提交于
      This patch implements the driver necessary use the Analog Devices
      Blackfin processor's on-chip ethernet MAC controller.
      
      [try#2]
       - add timeout control
       - kill dma_config_reg bitfields
       - some trivial cleanup
      
      [try#3]
       - add endianess check
       - add DRV_NAME, DRV_VERSION... driver information string
       - add some comments for silicon anomaly and dma API confusion
       - some code trivial cleanup
      
      [try#4]
       - add Blackfin latest GPIO pin mux opertion with Michael Hennerich's
        help and Dan's review
       - rewrite the DMA descriptor list operation in a more readable way
        by Joe's review
      
      [try#5]
       - cleanup some coding style by Joe's review.
      
      [try#6]
       - 1.1 version fix a bug when set up multicast list pointed by Mr. yoshfuji
       - rearrange the desc_list_free function.
      Signed-off-by: NMichael Hennerich <michael.hennerich@analog.com>
      Signed-off-by: NBryan Wu <bryan.wu@analog.com>
      Cc: Michael Buesch <mb@bu3sch.de>
      Cc: Mike Frysinger <vapier.adi@gmail.com>
      Cc: Jeff Garzik <jeff@garzik.org>
      Cc: Christoph Hellwig <hch@infradead.org>
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Joe Perches <joe@perches.com>
      Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      e190d6b1
  11. 18 7月, 2007 1 次提交
  12. 16 7月, 2007 2 次提交
  13. 15 7月, 2007 1 次提交
  14. 11 7月, 2007 4 次提交
    • J
      [L2TP]: PPP over L2TP driver core · 3557baab
      James Chapman 提交于
      This driver handles only L2TP data frames; control frames are handled
      by a userspace application. It implements L2TP using the PPPoX socket
      family. There is a PPPoX socket for each L2TP session in an L2TP
      tunnel.  PPP data within each session is passed through the kernel's
      PPP subsystem via this driver. Kernel parameters of each socket can be
      read or modified using ioctl() or [gs]etsockopt() calls.
      Signed-off-by: NJames Chapman <jchapman@katalix.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3557baab
    • M
      ps3: gigabit ethernet driver for PS3, take3 · 02c18891
      Masakazu Mokuno 提交于
      Hi,
      
      This is the third submission of the network driver for PS3.
      The differences from the previous one are:
      
        - renamed source file names so that their prefix can match
          with the module name
        - added cbe-oss-dev@ozlabs.org line for MAINTAINER file
        - changed some in copyright comments
      
      If there are no more comments, please apply for 2.6.23.
      
      Thank you
      
      --
      Subject: PS3: Ethernet driver
      
      From: Masakazu Mokuno <mokuno@sm.sony.co.jp>
      
      Add Gigabit Ethernet support for the PS3 game console.  The module will
      be called ps3_gelic.
      
      CC: Geoff Levand <geoffrey.levand@am.sony.com>
      Signed-off-by: NMasakazu Mokuno <mokuno@sm.sony.co.jp>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      02c18891
    • J
      Remove sk98lin ethernet driver. · e1abecc4
      Jeff Garzik 提交于
      Unmaintained, superceded by skge.
      
      Prodded to deletion by Adrian Bunk.  Acked by Stephen Hemminger.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      e1abecc4
    • B
      AX88796 network driver · 825a2ff1
      Ben Dooks 提交于
      Support for the Asix AX88796 network controller, an
      NE2000 compatible 10/100 ethernet device with internal
      PHY.
      
      The driver supports PHY settings via either ioctl() or
      the ethtool driver ops.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      825a2ff1
  15. 09 7月, 2007 1 次提交
  16. 10 5月, 2007 1 次提交
  17. 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
  18. 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
  19. 26 4月, 2007 1 次提交
  20. 08 2月, 2007 1 次提交
  21. 06 2月, 2007 5 次提交
  22. 02 12月, 2006 2 次提交
    • 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