1. 11 1月, 2011 1 次提交
  2. 29 9月, 2010 10 次提交
  3. 03 8月, 2010 3 次提交
    • D
      pcmcia: do not use io_req_t when calling pcmcia_request_io() · 90abdc3b
      Dominik Brodowski 提交于
      Instead of io_req_t, drivers are now requested to fill out
      struct pcmcia_device *p_dev->resource[0,1] for up to two ioport
      ranges. After a call to pcmcia_request_io(), the ports found there
      are reserved, after calling pcmcia_request_configuration(), they may
      be used.
      
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-ide@vger.kernel.org
      CC: linux-usb@vger.kernel.org
      CC: laforge@gnumonks.org
      CC: linux-mtd@lists.infradead.org
      CC: alsa-devel@alsa-project.org
      CC: linux-serial@vger.kernel.org
      CC: Michael Buesch <mb@bu3sch.de>
      Acked-by: Marcel Holtmann <marcel@holtmann.org> (for drivers/bluetooth/)
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      90abdc3b
    • D
      pcmcia: do not use io_req_t after call to pcmcia_request_io() · 9a017a91
      Dominik Brodowski 提交于
      After pcmcia_request_io(), do not make use of the values stored in
      io_req_t, but instead use those found in struct pcmcia_device->resource[].
      
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-ide@vger.kernel.org
      CC: linux-usb@vger.kernel.org
      CC: laforge@gnumonks.org
      CC: linux-mtd@lists.infradead.org
      CC: alsa-devel@alsa-project.org
      CC: linux-serial@vger.kernel.org
      Acked-by: Marcel Holtmann <marcel@holtmann.org> (for drivers/bluetooth/)
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      9a017a91
    • D
      pcmcia: use pcmica_{read,write}_config_byte · 1d5cc192
      Dominik Brodowski 提交于
      Use pcmcia_read_config_byte and pcmcia_write_config_byte instead
      of pcmcia_access_configuration_register.
      
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-serial@vger.kernel.org
      CC: Michael Buesch <mb@bu3sch.de>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      1d5cc192
  4. 31 7月, 2010 1 次提交
    • D
      pcmcia: remove cs_types.h · ac8b4228
      Dominik Brodowski 提交于
      Remove cs_types.h which is no longer needed: Most definitions aren't
      used at all, a few can be made away with, and two remaining definitions
      (typedefs, unfortunatley) may be moved to more specific places.
      
      CC: linux-ide@vger.kernel.org
      CC: linux-usb@vger.kernel.org
      CC: laforge@gnumonks.org
      CC: linux-mtd@lists.infradead.org
      CC: alsa-devel@alsa-project.org
      CC: linux-serial@vger.kernel.org
      Acked-by: Marcel Holtmann <marcel@holtmann.org> (for drivers/bluetooth/)
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      ac8b4228
  5. 16 6月, 2010 1 次提交
  6. 10 5月, 2010 2 次提交
    • D
      pcmcia: dev_node removal (write-only drivers) · 317b6d63
      Dominik Brodowski 提交于
      dev_node_t was only used to transport some minor/major numbers
      from the PCMCIA device drivers to deprecated userspace helpers.
      However, only a few drivers made use of it, and the userspace
      helpers are deprecated anyways. Therefore, get rid of dev_node_t .
      
      As a first step, remove any usage of dev_node_t from drivers which
      only wrote to this typedef/struct, but did not make use of it.
      
      CC: linux-bluetooth@vger.kernel.org
      CC: Harald Welte <laforge@gnumonks.org>
      CC: linux-mtd@lists.infradead.org
      CC: linux-wireless@vger.kernel.org
      CC: netdev@vger.kernel.org
      CC: linux-serial@vger.kernel.org
      CC: alsa-devel@alsa-project.org
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      317b6d63
    • D
      pcmcia: re-work pcmcia_request_irq() · eb14120f
      Dominik Brodowski 提交于
      Instead of the old pcmcia_request_irq() interface, drivers may now
      choose between:
      
      - calling request_irq/free_irq directly. Use the IRQ from *p_dev->irq.
      
      - use pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
        clean up automatically on calls to pcmcia_disable_device() or
        device ejection.
      
      - drivers still not capable of IRQF_SHARED (or not telling us so) may
        use the deprecated pcmcia_request_exclusive_irq() for the time
        being; they might receive a shared IRQ nonetheless.
      
      CC: linux-bluetooth@vger.kernel.org
      CC: netdev@vger.kernel.org
      CC: linux-wireless@vger.kernel.org
      CC: linux-serial@vger.kernel.org
      CC: alsa-devel@alsa-project.org
      CC: linux-usb@vger.kernel.org
      CC: linux-ide@vger.kernel.org
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      eb14120f
  7. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  8. 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
  9. 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
  10. 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
  11. 25 7月, 2009 1 次提交
  12. 31 8月, 2008 1 次提交
  13. 23 8月, 2008 5 次提交
  14. 08 7月, 2008 1 次提交
  15. 01 7月, 2008 1 次提交
  16. 21 5月, 2008 1 次提交
  17. 01 2月, 2008 1 次提交
  18. 29 1月, 2008 1 次提交
  19. 11 10月, 2007 3 次提交
  20. 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