1. 21 8月, 2015 1 次提交
  2. 07 1月, 2015 1 次提交
  3. 19 10月, 2013 4 次提交
  4. 11 10月, 2013 1 次提交
  5. 23 7月, 2013 1 次提交
  6. 19 7月, 2013 1 次提交
    • G
      rt2x00: RT2X00 should depend on HAS_DMA · 6a084839
      Geert Uytterhoeven 提交于
      If NO_DMA=y:
      
      drivers/built-in.o: In function `rt2x00queue_unmap_skb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:129: undefined reference to `dma_unmap_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:133: undefined reference to `dma_unmap_single'
      drivers/built-in.o: In function `rt2x00queue_map_txskb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:112: undefined reference to `dma_map_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:115: undefined reference to `dma_mapping_error'
      drivers/built-in.o: In function `rt2x00queue_alloc_rxskb':
      drivers/net/wireless/rt2x00/rt2x00queue.c:93: undefined reference to `dma_map_single'
      drivers/net/wireless/rt2x00/rt2x00queue.c:95: undefined reference to `dma_mapping_error'
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Cc: linux-wireless@vger.kernel.org
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      6a084839
  7. 04 4月, 2013 1 次提交
    • G
      rt2x00: rt2x00pci: fix build error on Ralink RT3x5x SoCs · 69a2bac8
      Gabor Juhos 提交于
      The rt2800pci driver supports the built-in wireless
      MAC of the Ralink RT3x5x SoCs. However building the
      driver for these SoCs leads to the following error:
      
          LD      init/built-in.o
        drivers/built-in.o: In function `rt2800pci_rxdone_tasklet':
        <...>/drivers/net/wireless/rt2x00/rt2800pci.c:1012: undefined reference to `rt2x00pci_rxdone'
        drivers/built-in.o:(.rodata+0x4780): undefined reference to `rt2x00pci_initialize'
        drivers/built-in.o:(.rodata+0x4784): undefined reference to `rt2x00pci_uninitialize'
        drivers/built-in.o:(.rodata+0x47bc): undefined reference to `rt2x00pci_flush_queue'
        drivers/built-in.o:(.rodata+0x4818): undefined reference to `rt2x00pci_regbusy_read'
        make[5]: *** [vmlinux] Error 1
      
      The missing functions are provided by the rt2x00pci
      module. This module is only selected by the rt2800pci
      driver if PCI support is enabled in the kernel, because
      some parts of the rt2x00pci code depends on PCI support.
      
      PCI support is not available on the RT3x5x SoCs because
      those have no PCI host controller at all.
      
      Move the non PCI specific code from rt2x00pci into a
      separate module. This makes it possible to use that
      code even if PCI support is disabled. The affected
      functions are used by all of the rt2x00 PCI drivers
      so select the new module for those drivers.
      Signed-off-by: NGabor Juhos <juhosg@openwrt.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      69a2bac8
  8. 19 3月, 2013 1 次提交
  9. 14 3月, 2013 1 次提交
  10. 23 1月, 2013 1 次提交
  11. 21 6月, 2012 1 次提交
  12. 23 2月, 2012 1 次提交
  13. 02 6月, 2011 1 次提交
  14. 28 5月, 2011 1 次提交
  15. 06 5月, 2011 1 次提交
  16. 20 4月, 2011 3 次提交
  17. 22 2月, 2011 1 次提交
  18. 18 11月, 2010 4 次提交
  19. 12 11月, 2010 1 次提交
  20. 05 5月, 2010 1 次提交
  21. 16 2月, 2010 1 次提交
    • G
      rt2x00: rt2800 - Make rt30xx and rt35xx chipsets configurable. · de1ebdce
      Gertjan van Wingerde 提交于
      Support for rt30xx- and rt35xx-based devices is currently not functional
      in rt2800pci and rt2800usb.
      In order to not confuse users we shouldn't claim the PCI and USB device
      ID's for these devices. However, to allow for testing it is good to still
      have them available, although disabled by default.
      Make support for these device configuration options that default to off.
      
      For rt2800usb a 3rd class of devices is added, which are the unknown
      devices. For these devices it is known that they are either based on
      rt28xx, rt30xx or rt35xx, but it is not known on what chipset exactly.
      These devices are disabled by default as well, until it can be established
      on what chipset exactly they are based.
      Signed-off-by: NGertjan van Wingerde <gwingerde@gmail.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      de1ebdce
  22. 29 12月, 2009 1 次提交
  23. 07 11月, 2009 1 次提交
  24. 05 11月, 2009 2 次提交
  25. 31 10月, 2009 1 次提交
  26. 28 10月, 2009 2 次提交
  27. 05 8月, 2009 1 次提交
  28. 11 7月, 2009 1 次提交
  29. 13 6月, 2009 1 次提交
  30. 07 5月, 2009 1 次提交