1. 01 Aug, 2008 10 commits
  2. 31 Jul, 2008 7 commits
  3. 30 Jul, 2008 21 commits
  4. 29 Jul, 2008 2 commits
    • Breno Leitao's avatar
      S2io: fix statistics flush after a MTU change · dc56e634
      Breno Leitao authored
      On s2io driver, when you change the interface MTU, it invokes a card
      reset, which flush some statistics.  This patch solves this problem, and
      also set the net_device->stats as the default statistics structure,
      instead of s2io_nic->stats.
      
      To do that, s2io_nic->stats turned into a staging area, where is saved
      statistics of the last hardware statistics query. So, the difference
      between the current hardware statistics and s2io_nic->stats, is the
      value that should be summed up, in order to get the correct statistics
      value, even after a reset.
      Signed-off-by: default avatarBreno Leitao <leitao@linux.vnet.ibm.com>
      Signed-off-by: default avatarJay Vosburgh <fubar@us.ibm.com>
      Signed-off-by: default avatarJeff Garzik <jgarzik@redhat.com>
      dc56e634
    • David Brownell's avatar
      enc28j60: don't specify (wrong) IRQ type · c7b7b042
      David Brownell authored
      Recent changes to the IRQ framework have made passing the wrong
      trigger type to request_irq() become a fatal error.  In the case
      of the enc28j60 driver, it stopped working in my test harness.
      
      (Specifically:  the signal detects "pin change" events, both edges,
      not just falling edges.  Similarly, other boards might route it
      through an inverter.  Trigger type are board-specific.)
      
      This fixes that problem by the usual fix of expecting board setup
      code to have set up the correct IRQ trigger type.  The best known
      example of that being x86 setup.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarJeff Garzik <jgarzik@redhat.com>
      c7b7b042