1. 04 12月, 2012 1 次提交
  2. 10 7月, 2012 1 次提交
  3. 08 7月, 2012 1 次提交
  4. 30 5月, 2012 2 次提交
  5. 13 4月, 2012 8 次提交
  6. 04 4月, 2012 1 次提交
  7. 16 2月, 2012 1 次提交
  8. 01 2月, 2012 1 次提交
  9. 08 1月, 2012 1 次提交
    • C
      r6040: fix typo in use of MCR0 register bits · 77e1e438
      Cesar Eduardo Barros 提交于
      Commit 4e16d6eb (r6040: define more MCR0
      register bits) added #define values for MCR0 register bits and converted
      uses of hardcoded magic values to uses of these defines.
      
      However, one of the conversions looks suspicious:
      
       #define MCR0		0x00	/* Control register 0 */
      +#define  MCR0_RCVEN	0x0002	/* Receive enable */
      +#define  MCR0_XMTEN	0x1000	/* Transmission enable */
      
       	/* Init RDC private data */
      -	lp->mcr0 = 0x1002;
      +	lp->mcr0 = MCR0_XMTEN | MCR0;
      
      I believe what was meant here was MCR0_XMTEN | MCR0_RCVEN, which makes
      sense and matches the original values.
      Signed-off-by: NCesar Eduardo Barros <cesarb@cesarb.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      77e1e438
  10. 05 1月, 2012 7 次提交
  11. 17 11月, 2011 1 次提交
  12. 10 10月, 2011 2 次提交
  13. 18 8月, 2011 1 次提交
  14. 13 8月, 2011 1 次提交
  15. 15 7月, 2011 1 次提交
  16. 20 6月, 2011 1 次提交
  17. 14 6月, 2011 1 次提交
  18. 31 3月, 2011 1 次提交
  19. 09 3月, 2011 2 次提交
  20. 24 2月, 2011 2 次提交
  21. 07 1月, 2011 1 次提交
  22. 19 10月, 2010 1 次提交
    • B
      r6040: Fix multicast filter some more · e2269308
      Ben Hutchings 提交于
      This code has been broken forever, but in several different and
      creative ways.
      
      So far as I can work out, the R6040 MAC filter has 4 exact-match
      entries, the first of which the driver uses for its assigned unicast
      address, plus a 64-entry hash-based filter for multicast addresses
      (maybe unicast as well?).
      
      The original version of this code would write the first 4 multicast
      addresses as exact-match entries from offset 1 (bug #1: there is no
      entry 4 so this could write to some PHY registers).  It would fill the
      remainder of the exact-match entries with the broadcast address (bug #2:
      this would overwrite the last used entry).  If more than 4 multicast
      addresses were configured, it would set up the hash table, write some
      random crap to the MAC control register (bug #3) and finally walk off
      the end of the list when filling the exact-match entries (bug #4).
      
      All of this seems to be pointless, since it sets the promiscuous bit
      when the interface is made promiscuous or if >4 multicast addresses
      are enabled, and never clears it (bug #5, masking bug #2).
      
      The recent(ish) changes to the multicast list fixed bug #4, but
      completely removed the limit on iteration over the exact-match entries
      (bug #6).
      
      Bug #4 was reported as
      <https://bugzilla.kernel.org/show_bug.cgi?id=15355> and more recently
      as <http://bugs.debian.org/600155>.  Florian Fainelli attempted to fix
      these in commit 3bcf8229, but that
      actually dealt with bugs #1-3, bug #4 having been fixed in mainline at
      that point.
      
      That commit fixes the most important current bug #6.
      Signed-off-by: NBen Hutchings <ben@decadent.org.uk>
      Cc: stable@kernel.org [2.6.35 only]
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e2269308
  23. 27 9月, 2010 1 次提交