1. 28 6月, 2008 1 次提交
  2. 25 6月, 2008 3 次提交
  3. 24 6月, 2008 1 次提交
  4. 18 6月, 2008 1 次提交
  5. 12 6月, 2008 2 次提交
  6. 09 6月, 2008 1 次提交
  7. 04 6月, 2008 1 次提交
  8. 31 5月, 2008 2 次提交
  9. 29 5月, 2008 1 次提交
  10. 22 5月, 2008 2 次提交
  11. 13 5月, 2008 1 次提交
  12. 07 5月, 2008 1 次提交
  13. 29 4月, 2008 2 次提交
  14. 28 4月, 2008 1 次提交
  15. 24 4月, 2008 1 次提交
  16. 17 4月, 2008 1 次提交
  17. 29 3月, 2008 1 次提交
  18. 28 3月, 2008 1 次提交
  19. 26 3月, 2008 1 次提交
  20. 17 3月, 2008 1 次提交
  21. 12 3月, 2008 1 次提交
  22. 05 3月, 2008 1 次提交
  23. 24 4月, 2008 1 次提交
  24. 28 2月, 2008 1 次提交
  25. 27 2月, 2008 1 次提交
  26. 12 2月, 2008 1 次提交
  27. 11 2月, 2008 1 次提交
  28. 09 2月, 2008 1 次提交
  29. 06 2月, 2008 1 次提交
    • A
      cpmac: convert to new Fixed PHY infrastructure · 8353ec7b
      Anton Vorontsov 提交于
      This patch converts cpmac to the new Fixed PHY infrastructure, though it
      doesn't fix all the problems with that driver. I didn't even bother to
      test this patch to compile, because cpmac driver is broken in several ways:
      
      1. This driver won't compile by itself because lack of its header describing
         platform data;
      2. It assumes that fixed PHYs should be created by the ethernet driver.
         It is wrong assumption: fixed PHYs creation is platform code authority,
         driver must blindly accept bus_id and phy_id platform data variables
         instead.
      
      Also, it seem that that driver doesn't have actual in-tree users, so
      nothing to fix further.
      
      The main purpose of that patch is to get rid of the following Kconfig
      warning:
      
      scripts/kconfig/conf -s arch/powerpc/Kconfig
      drivers/net/Kconfig:1713:warning: 'select' used by config symbol
      'CPMAC' refers to undefined symbol 'FIXED_MII_100_FDX'
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      8353ec7b
  30. 05 2月, 2008 1 次提交
  31. 04 2月, 2008 1 次提交
  32. 03 2月, 2008 2 次提交
  33. 30 1月, 2008 1 次提交
    • L
      [net] Gracefully handle shared e1000/1000e driver PCI ID's · 60e23317
      Linus Torvalds 提交于
      Both the old e1000 driver and the new e1000e driver can drive some
      PCI-Express e1000 cards, and we should avoid ambiguity about which
      driver will pick up the support for those cards when both drivers are
      enabled.
      
      This solves the problem by having the old driver support those cards if
      the new driver isn't configured, but otherwise ceding support for PCI
      Express versions of the e1000 chipset to the newer driver.  Thus
      allowing both legacy configurations where only the old driver is active
      (and handles all chips it knows about) and the new configuration with
      the new driver handling the more modern PCIE variants.
      Acked-by: NJeff Garzik <jeff@garzik.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      60e23317