1. 20 2月, 2010 1 次提交
    • P
      Introduce PCMCIA_DEVICE_PROD_ID3 · fbc87d67
      Pavel Roskin 提交于
      ...and use it in hostap_cs and orinoco_cs.
      
      Another PCMCIA device with Intersil Prism chipset has been reported:
      
      Socket 0:
        product info: "Gigabyte", "GN-WLM01_P25L_ADAPTER", "ISL37300P", "Eval-RevA"
        manfid: 0x02e0, 0x1011
        function: 6 (network)
      
      As it's the case with some other Prism based devices, the third ID
      string contains a design name that should be sufficient to identify the
      card as having Intersil Prism chipset and thus compatible with both
      orinoco_cs and hostap_cs.
      
      Introduce PCMCIA_DEVICE_PROD_ID3 that matches the third ID string only.
      
      Use it in orinoco_cs and hostap_cs to match cards with the third ID
      string indicating Prism chipset.  Remove corresponding entries that use
      PCMCIA_DEVICE_PROD_ID123.
      Reported-by: NOzzy <ozzymud@gmail.com>
      Signed-off-by: NPavel Roskin <proski@gnu.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      fbc87d67
  2. 29 11月, 2009 2 次提交
    • D
      pcmcia: rework the irq_req_t typedef · 5fa9167a
      Dominik Brodowski 提交于
      Most of the irq_req_t typedef'd struct can be re-worked quite
      easily:
      
      (1) IRQInfo2 was unused in any case, so drop it.
      
      (2) IRQInfo1 was used write-only, so drop it.
      
      (3) Instance (private data to be passed to the IRQ handler):
      	Most PCMCIA drivers using pcmcia_request_irq() to actually
      	register an IRQ handler set the "dev_id" to the same pointer
      	as the "priv" pointer in struct pcmcia_device. Modify the two
      	exceptions (ipwireless, ibmtr_cs) to also work this waym and
      	set the IRQ handler's "dev_id" to p_dev->priv unconditionally.
      
      (4) Handler is to be of type irq_handler_t.
      
      (5) Handler != NULL already tells whether an IRQ handler is present.
      	Therefore, we do not need the IRQ_HANDLER_PRESENT flag in
      	irq_req_t.Attributes.
      
      CC: netdev@vger.kernel.org
      CC: linux-bluetooth@vger.kernel.org
      CC: linux-ide@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-scsi@vger.kernel.org
      CC: alsa-devel@alsa-project.org
      CC: Jaroslav Kysela <perex@perex.cz>
      CC: Jiri Kosina <jkosina@suse.cz>
      CC: Karsten Keil <isdn@linux-pingi.de>
      for the Bluetooth parts: Acked-by: Marcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      5fa9167a
    • D
      pcmcia: remove deprecated handle_to_dev() macro · dd2e5a15
      Dominik Brodowski 提交于
      Update remaining users and remove deprecated handle_to_dev() macro
      
      CC: Harald Welte <laforge@gnumonks.org>
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-serial@vger.kernel.org
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      dd2e5a15
  3. 09 11月, 2009 2 次提交
    • D
      pcmcia: use dynamic debug infrastructure, deprecate CS_CHECK (wireless) · 2caff147
      Dominik Brodowski 提交于
      Convert PCMCIA drivers to use the dynamic debug infrastructure, instead of
      requiring manual settings of PCMCIA_DEBUG.
      
      Also, remove all usages of the CS_CHECK macro and replace them with proper
      Linux style calling and return value checking. The extra error reporting may
      be dropped, as the PCMCIA core already complains about any (non-driver-author)
      errors.
      
      CC: linux-wireless@vger.kernel.org
      CC: netdev@vger.kernel.org
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      2caff147
    • D
      pcmcia: use pre-determined values · 7d2e8d00
      Dominik Brodowski 提交于
      A few PCMCIA network drivers can make use of values provided by the pcmcia
      core, instead of tedious, independent CIS parsing.
      
      xirc32ps_cs.c: manf_id
      
      hostap_cs.c: multifunction count
      
      b43/pcmcia.c: ConfigBase address and "Present"
      
      smc91c92_cs.c:  By default, mhz_setup() can use VERS_1 as it is stored
      in struct pcmcia_device. Only some cards require workarounds, such as
      reading out VERS_1 twice.
      
      CC: David S. Miller <davem@davemloft.net>
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      Acked-by: NJohn W. Linville <linville@tuxdriver.com>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      7d2e8d00
  4. 25 7月, 2009 1 次提交
  5. 31 8月, 2008 1 次提交
  6. 23 8月, 2008 5 次提交
  7. 08 7月, 2008 1 次提交
  8. 01 7月, 2008 1 次提交
  9. 21 5月, 2008 1 次提交
  10. 01 2月, 2008 1 次提交
  11. 29 1月, 2008 1 次提交
  12. 11 10月, 2007 3 次提交
  13. 09 7月, 2007 1 次提交
    • J
      [PATCH] hostap: Remove driver version number · bd5824f1
      Jouni Malinen 提交于
      The driver version number has not been updated since the driver was
      included in the main kernel tree and there is no plan on updating this
      in the future either. At this point, the only correct way to refer to
      the version is to use the kernel version. The 0.4.4 version is
      confusing since there are external version with higher version number
      even though they are not actually any newer than the in-tree version.
      
      Let's get rid of the version number in the kernel tree in order to
      avoid this kind of confusion.
      Signed-off-by: NJouni Malinen <j@w1.fi>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      bd5824f1
  14. 28 4月, 2007 3 次提交
  15. 06 12月, 2006 1 次提交
  16. 05 12月, 2006 2 次提交
  17. 26 10月, 2006 1 次提交
  18. 12 9月, 2006 1 次提交
  19. 01 7月, 2006 2 次提交
  20. 23 5月, 2006 1 次提交
  21. 31 3月, 2006 8 次提交