1. 10 5月, 2012 1 次提交
    • J
      ixgbe: Hardware Timestamping + PTP Hardware Clock (PHC) · 3a6a4eda
      Jacob Keller 提交于
      This patch enables hardware timestamping for use with PTP software by
      extracting a ns counter from an arbitrary fixed point cycles counter.
      The hardware generates SYSTIME registers using the DMA tick which
      changes based on the current link speed. These SYSTIME registers are
      converted to ns using the cyclecounter and timecounter structures
      provided by the kernel. Using the SO_TIMESTAMPING api, software can
      enable and access timestamps for PTP packets.
      
      The SO_TIMESTAMPING API has space for 3 different kinds of timestamps,
      SYS, RAW, and SOF. SYS hardware timestamps are hardware ns values that
      are then scaled to the software clock. RAW hardware timestamps are the
      direct raw value of the ns counter. SOF software timestamps are the
      software timestamp calculated as close as possible to the software
      transmit, but are not offloaded to the hardware. This patch only
      supports the RAW hardware timestamps due to inefficiency of the SYS
      design.
      
      This patch also enables the PHC subsystem features for atomically
      adjusting the cycle register, and adjusting the clock frequency in
      parts per billion. This frequency adjustment works by slightly
      adjusting the value added to the cycle registers each DMA tick. This
      causes the hardware registers to overflow rapidly (approximately once
      every 34 seconds, when at 10gig link). To solve this, the timecounter
      structure is used, along with a timer set for every 25 seconds. This
      allows for detecting register overflow and converting the cycle
      counter registers into ns values needed for providing useful
      timestamps to the network stack.
      
      Only the basic required clock functions are supported at this time,
      although the hardware supports some ancillary features and these could
      easily be enabled in the future.
      
      Note that use of this hardware timestamping requires modifying daemon
      software to use the SO_TIMESTAMPING API for timestamps, and the
      ptp_clock PHC framework for accessing the clock. The timestamps have
      no relation to the system time at all, so software must use the posix
      clock generated by the PHC framework instead.
      Signed-off-by: NJacob E Keller <jacob.e.keller@intel.com>
      Tested-by: NStephen Ko <stephen.s.ko@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      3a6a4eda
  2. 02 5月, 2012 1 次提交
  3. 20 3月, 2012 1 次提交
    • J
      ixgbe: fix namespace issues when FCoE/DCB is not enabled · 8af3c33f
      Jeff Kirsher 提交于
      Resolve namespace issues when FCoE or DCB is not enabled.
      The issue is with certain configurations we end up with namespace
      problems. A simple example:
      
      ixgbe_main.c
       - defines func A()
       - uses func A()
      
      ixgbe_fcoe.c
       - uses func A()
      
      ixgbe.h
       - has prototype for func A()
      
      For default (FCoE included) all is good.  But when it isn't the namespace
      checker complains about how func A() could be static.
      
      To resolve this, created a ixgbe_lib file to contain functions used
      by DCB/FCoE and their helper functions so that they are always in
      namespace whether or not DCB/FCoE is enabled.
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      Tested-by: NPhil Schmitt <phillip.j.schmitt@intel.com>
      8af3c33f
  4. 03 2月, 2012 1 次提交
  5. 11 8月, 2011 1 次提交
  6. 17 11月, 2010 1 次提交
  7. 14 1月, 2010 1 次提交
  8. 11 1月, 2010 1 次提交
  9. 18 5月, 2009 1 次提交
  10. 01 3月, 2009 1 次提交
  11. 01 2月, 2009 1 次提交
  12. 25 11月, 2008 1 次提交
  13. 21 11月, 2008 1 次提交
  14. 11 10月, 2007 2 次提交
    • A
      ixgbe: driver for Intel(R) 82598 PCI-Express 10GbE adapters (v4) · 9a799d71
      Auke Kok 提交于
      This patch adds support for the Intel 82598 PCI-Express 10GbE
      chipset. Devices will be available on the market soon.
      
      This version of the driver is largely the same as the last release:
      
        * Driver uses a single RX and single TX queue, each using 1 MSI-X
        irq vector.
        * Driver runs in NAPI mode only
        * Driver is largely multiqueue-ready (TM)
      
      Changes since 20070803:
        * removed wrappers for hardware functions
        * incorporated e1000e-style HW api reorganization code
        * sparse/checkpatch cleanups, namespace cleanups
        * driver prints out extra debugging information at load time
          identifying adapter board number, mac, phy types
        * removed ixgbe_api.c, ixgbe_api.h, ixgbe_osdep.h
        * driver update to 1.1.18
        * removed ixgbe.txt which contained no useful info anymore
      
      [ Integrated napi_struct changes from Auke as well... -DaveM ]
      Signed-off-by: NAuke Kok <auke-jan.h.kok@intel.com>
      Signed-off-by: NAyyappan Veeraiyan <ayyappan.veeraiyan@intel.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9a799d71
    • A
      [E1000E]: New pci-express e1000 driver (currently for ICH9 devices only) · bc7f75fa
      Auke Kok 提交于
      This driver implements support for the ICH9 on-board LAN ethernet
      device. The device is similar to ICH8.
      
      The driver encompasses code to support 82571/2/3, es2lan and ICH8
      devices as well, but those device IDs are disabled and will be
      "lifted" from the e1000 driver over one at a time once this driver
      receives some more live time.
      
      Changes to the last snapshot posted are exclusively in the internal
      hardware API organization. Many thanks to Jeff Garzik for jumping in
      and getting this organized with a keen eye on the future layout.
      
      [ Integrated napi_struct patch from Auke as well... -DaveM ]
      Signed-off-by: NAuke Kok <auke-jan.h.kok@intel.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bc7f75fa
  15. 28 9月, 2006 1 次提交
  16. 24 5月, 2006 1 次提交
  17. 15 4月, 2006 1 次提交
  18. 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