1. 25 9月, 2008 1 次提交
  2. 17 3月, 2008 1 次提交
  3. 18 2月, 2007 1 次提交
    • J
      bugfixes and new hardware support for arcnet driver · 52edc17f
      Jeff Morrow 提交于
      The modifications and bug fixes noted below were done by Realtime Control
      Works and Contemporary Control Systems, Inc, Jan 2005.  They were
      incorporated into the 2.6 kernel by Jeff Morrow of Sierra Analytics, Feb
      2007.  <jmorrow@massspec.com>
      
      The changes have been tested on a Contemporary Controls PCI20U-4000.
      
      Summary of changes:
      
      Arc-rawmode.c:
            rx():
            - Fixed error in received packet lengths; 256 byte packets were
              being received as 257 bytes packets.
      
            prepare_tx():
            - Fixed error in transmit length calcs; 257 byte packets were being
              transmitted as 260 byte packets.
      
      com20020.c:
            com20020_check():
            - We now load the SETUP2 register if the 'clockm' parameter is
              non-zero, instead of checking for ARC_CAN_10MBIT. The user is
              now responsible for whether or not SETUP2 is loaded.  If the
              clock multiplier is non-zero, this means that the user wants a
              baud rate greater than 2.5Mbps. This is not possible unless the
              SETUP2 register is present (COM20020D, or COM20022). So, we're
              relying on the user to be smart about what kind of chip he's
              dealing with...
      
      com20020-pci.c
            - Added several entries to com20020pci_id_table[].
      Signed-off-by: NJeff Morrow <jmorrow@massspec.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      52edc17f
  4. 13 2月, 2007 1 次提交
  5. 11 11月, 2006 1 次提交
  6. 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