1. 18 2月, 2010 4 次提交
  2. 25 1月, 2010 3 次提交
  3. 29 11月, 2009 3 次提交
  4. 09 11月, 2009 3 次提交
    • D
      pcmcia: use dynamic debug instead of custom infrastructure · d50dbec3
      Dominik Brodowski 提交于
      Use the generic "dynamic debug" infrastructure instead of
      CONIG_PCMCIA_DEBUG in the PCMCIA core (pcmcia.ko and pcmcia_core.ko). To
      enable debugging, enable CONFIG_DYNAMIC_DEBUG, mount debugfs and
      
      $ echo -n 'module pcmcia_core +p' > /sys/kernel/debug/dynamic_debug/control
      
      for the complete module "pcmcia_core", for example. For more detailled
      instructions, please see Documentation/dynamic-debug-howto.txt
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      d50dbec3
    • D
      pcmcia: remove pcmcia_get_{first,next}_tuple() · 18a7a19b
      Dominik Brodowski 提交于
      Remove the pcmcia_get_{first,next}_tuple() calls no longer needed by
      (current) pcmcia device drivers.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      18a7a19b
    • D
      pcmcia: add new CIS access helpers · 91284224
      Dominik Brodowski 提交于
      As a replacement to pcmcia_get_{first,next}_tuple() and
      pcmcia_get_tuple_data(), three new -- and easier to use --
      functions are added:
      
      - pcmcia_get_tuple() to get the very first CIS entry of one
        type.
      
      - pcmcia_loop_tuple() to loop over all CIS entries of one type.
      
      - pcmcia_get_mac_from_cis() to read out the hardware MAC address
        from CISTPL_FUNCE.
      
      Only a handful of drivers need these functions anyway, as most
      CIS access is already handled by pcmcia_loop_config(), which
      now shares the same backed (pccard_loop_tuple()) with
      pcmcia_loop_tuple().
      
      A pcmcia_get_mac_from_cis() bug noted by Komuro
      <komurojun-mbn@nifty.com> has been fixed in this revision.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      91284224
  5. 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
  6. 31 8月, 2008 2 次提交
  7. 26 8月, 2008 3 次提交
  8. 23 8月, 2008 5 次提交
  9. 24 6月, 2008 2 次提交
  10. 01 5月, 2008 1 次提交
  11. 08 2月, 2007 1 次提交
  12. 05 12月, 2006 1 次提交
  13. 31 3月, 2006 7 次提交
  14. 06 1月, 2006 2 次提交
  15. 10 9月, 2005 2 次提交