1. 25 3月, 2010 1 次提交
  2. 26 2月, 2010 1 次提交
    • D
      pcmcia: validate late-added resources · 7b4884ca
      Dominik Brodowski 提交于
      Currently, only those mem resources are validated which are already
      registered at the time the first PCMCIA card is inserted. As we can
      only validate resources immediately after card insert, store
      "registered" mem resources in mem_db, and only upon validation move
      them to mem_db_valid. When allocationg mem resources, mem_db_valid is
      then preferred to mem_db.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      7b4884ca
  3. 24 2月, 2010 1 次提交
  4. 23 2月, 2010 2 次提交
  5. 18 2月, 2010 5 次提交
  6. 18 1月, 2010 3 次提交
  7. 08 12月, 2009 1 次提交
    • D
      pcmcia: CodingStyle fixes · 9fea84f4
      Dominik Brodowski 提交于
      Fix several CodingStyle issues in drivers/pcmcia/ . checkpatch.pl no longer
      reports errors in the PCMCIA core. The remaining warnings mostly relate to
      wrong indent -- PCMCIA historically used 4 spaces --, to lines over 80
      characters and to hundreds of typedefs. The cleanup of those will follow
      in the future.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      9fea84f4
  8. 19 10月, 2009 1 次提交
    • D
      pcmcia: pccard_read_tuple and TUPLE_RETURN_COMMON cleanup · 84897fc0
      Dominik Brodowski 提交于
      pccard_read_tuple(), which is only used by the PCMCIA core, should
      handle TUPLE_RETURN_COMMON more sensibly: If a specific function (which
      may be 0) is requested, set tuple.Attributes = 0 as was done in all
      PCMCIA drivers. If, however, BIND_FN_ALL is requested, return the
      "common" tuple. As to the callers of pccard_read_tuple():
      
      - All calls to pcmcia_validate_cis() had set the "function" parameter to
        BIND_FN_ALL. Therefore, remove the "function" parameter and make the
        parameter to pccard_read_tuple explicit.
      
      - Calls to CISTPL_VERS_1 and CISTPL_MANFID now set BIND_FN_ALL. This was
        already the case for calls to CISTPL_LONGLINK_MFC.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      84897fc0
  9. 17 10月, 2009 1 次提交
  10. 02 11月, 2008 1 次提交
  11. 23 8月, 2008 3 次提交
  12. 28 7月, 2008 1 次提交
  13. 24 6月, 2008 4 次提交
  14. 01 5月, 2008 1 次提交
    • S
      pcmcia: silence section mismatch warnings from class_interface variables · ed49f5d0
      Sam Ravnborg 提交于
      Silence the following warnings:
      WARNING: drivers/pcmcia/built-in.o(.data+0x6e8): Section mismatch in reference from the variable pcmcia_bus_interface to the function .devinit.text:pcmcia_bus_add_socket()
      WARNING: drivers/pcmcia/built-in.o(.data+0xa88): Section mismatch in reference from the variable pccard_rsrc_interface to the function .devinit.text:pccard_sysfs_add_rsrc()
      WARNING: drivers/pcmcia/built-in.o(.data+0xa90): Section mismatch in reference from the variable pccard_rsrc_interface to the function .devexit.text:pccard_sysfs_remove_rsrc()
      
      The variables of type class_interface contains references
      to __devinit and __devexit functions which is OK.
      Silence warnings by annotating the variables with __refdata.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Dominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      ed49f5d0
  15. 06 2月, 2008 1 次提交
  16. 08 2月, 2007 1 次提交
  17. 28 6月, 2006 2 次提交
  18. 31 3月, 2006 2 次提交
  19. 06 1月, 2006 3 次提交
  20. 31 10月, 2005 1 次提交
  21. 29 10月, 2005 1 次提交
  22. 29 9月, 2005 2 次提交
  23. 28 6月, 2005 1 次提交
    • D
      [PATCH] ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees · b6d00f0d
      Dominik Brodowski 提交于
      Don't auto-configure yenta sockets for PCMCIA devices if it is connected to
      the root PCI bus on the x86 or x86_64 architectures.  Previously, this was
      handled by the "ioport_resource"/"iomem_resource" check a few lines below,
      but with the new ACPI-based resource handling this doesn't catch all cases
      any longer.
      
      pci-yenta-cardbus-fix.patch and this patch should solve the initialization
      time trouble.  However, the ACPI-based PCI resource handling is badly
      broken, IMHO:
      
      - many resources of devices don't show up in the resource trees (
        /proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but
        also possibly other subsystems (ISA, PnP, ...) do not know which resources
        it cannot use.
      
      - verify_root_windows() should fail if there are no iomem _or_ ioport
        resources, not only if there are no iomem _and_ ioport resources.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b6d00f0d