€•U§      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ)/translations/zh_CN/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/zh_TW/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/it_IT/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ja_JP/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/ko_KR/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ)/translations/sp_SP/pcmcia/driver-changes”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒDriver changes”h]”hŒDriver changes”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒC/var/lib/git/docbuild/linux/Documentation/pcmcia/driver-changes.rst”h KubhŒ	paragraph”“”)”}”(hŒIThis file details changes in 2.6 which affect PCMCIA card driver authors:”h]”hŒIThis file details changes in 2.6 which affect PCMCIA card driver authors:”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX‰  pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
 If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
 pcmcia_loop_config() now sets up certain configuration values
 automatically, though the driver may still override the settings
 in the callback function. The following autoconfiguration options
 are provided at the moment:

      - CONF_AUTO_CHECK_VCC : check for matching Vcc
      - CONF_AUTO_SET_VPP   : set Vpp
      - CONF_AUTO_AUDIO     : auto-enable audio line, if required
      - CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])
      - CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
”h]”hŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hX  pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
pcmcia_loop_config() now sets up certain configuration values
automatically, though the driver may still override the settings
in the callback function. The following autoconfiguration options
are provided at the moment:

     - CONF_AUTO_CHECK_VCC : check for matching Vcc
     - CONF_AUTO_SET_VPP   : set Vpp
     - CONF_AUTO_AUDIO     : auto-enable audio line, if required
     - CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])
     - CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
”h]”(hŒterm”“”)”}”(hŒ9pcmcia_loop_config() and autoconfiguration (as of 2.6.36)”h]”hŒ9pcmcia_loop_config() and autoconfiguration (as of 2.6.36)”…””}”(hhßhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h KhhÙubhŒ
definition”“”)”}”(hhh]”(h¸)”}”(hX  If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
pcmcia_loop_config() now sets up certain configuration values
automatically, though the driver may still override the settings
in the callback function. The following autoconfiguration options
are provided at the moment:”h]”(hŒIf ”…””}”(hhòhžhhŸNh NubhŒtitle_reference”“”)”}”(hŒ+`struct pcmcia_device *p_dev->config_flags`”h]”hŒ)struct pcmcia_device *p_dev->config_flags”…””}”(hhühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1húhhòubhŒñ is set accordingly,
pcmcia_loop_config() now sets up certain configuration values
automatically, though the driver may still override the settings
in the callback function. The following autoconfiguration options
are provided at the moment:”…””}”(hhòhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhïubhŒblock_quote”“”)”}”(hX  - CONF_AUTO_CHECK_VCC : check for matching Vcc
- CONF_AUTO_SET_VPP   : set Vpp
- CONF_AUTO_AUDIO     : auto-enable audio line, if required
- CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])
- CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
”h]”hÈ)”}”(hhh]”(hÍ)”}”(hŒ,CONF_AUTO_CHECK_VCC : check for matching Vcc”h]”h¸)”}”(hj  h]”hŒ,CONF_AUTO_CHECK_VCC : check for matching Vcc”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒCONF_AUTO_SET_VPP   : set Vpp”h]”h¸)”}”(hj6  h]”hŒCONF_AUTO_SET_VPP   : set Vpp”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj4  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒ9CONF_AUTO_AUDIO     : auto-enable audio line, if required”h]”h¸)”}”(hjM  h]”hŒ9CONF_AUTO_AUDIO     : auto-enable audio line, if required”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhjK  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒ<CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])”h]”h¸)”}”(hjd  h]”hŒ<CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khjb  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubhÍ)”}”(hŒ?CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
”h]”h¸)”}”(hŒ>CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])”h]”hŒ>CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhj  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hÇhŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h Khhïubeh}”(h]”h ]”h"]”h$]”h&]”uh1híhhÙubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KhhÔubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhhÎubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX5  pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
 pcmcia_request_configuration() got renamed to pcmcia_enable_device(),
 as it mirrors pcmcia_disable_device(). Configuration settings are now
 stored in struct pcmcia_device, e.g. in the fields config_flags,
 config_index, config_base, vpp.
”h]”hÓ)”}”(hhh]”hØ)”}”(hX1  pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
pcmcia_request_configuration() got renamed to pcmcia_enable_device(),
as it mirrors pcmcia_disable_device(). Configuration settings are now
stored in struct pcmcia_device, e.g. in the fields config_flags,
config_index, config_base, vpp.
”h]”(hÞ)”}”(hŒCpcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)”h]”hŒCpcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)”…””}”(hjÂ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Khj¾  ubhî)”}”(hhh]”h¸)”}”(hŒìpcmcia_request_configuration() got renamed to pcmcia_enable_device(),
as it mirrors pcmcia_disable_device(). Configuration settings are now
stored in struct pcmcia_device, e.g. in the fields config_flags,
config_index, config_base, vpp.”h]”hŒìpcmcia_request_configuration() got renamed to pcmcia_enable_device(),
as it mirrors pcmcia_disable_device(). Configuration settings are now
stored in struct pcmcia_device, e.g. in the fields config_flags,
config_index, config_base, vpp.”…””}”(hjÓ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhjÐ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj¾  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Khj»  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj·  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hXS  pcmcia_request_window changes (as of 2.6.36)
 Instead of win_req_t, drivers are now requested to fill out
 `struct pcmcia_device *p_dev->resource[2,3,4,5]` for up to four ioport
 ranges. After a call to pcmcia_request_window(), the regions found there
 are reserved and may be used immediately -- until pcmcia_release_window()
 is called.
”h]”hÓ)”}”(hhh]”hØ)”}”(hXN  pcmcia_request_window changes (as of 2.6.36)
Instead of win_req_t, drivers are now requested to fill out
`struct pcmcia_device *p_dev->resource[2,3,4,5]` for up to four ioport
ranges. After a call to pcmcia_request_window(), the regions found there
are reserved and may be used immediately -- until pcmcia_release_window()
is called.
”h]”(hÞ)”}”(hŒ,pcmcia_request_window changes (as of 2.6.36)”h]”hŒ,pcmcia_request_window changes (as of 2.6.36)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Khj   ubhî)”}”(hhh]”h¸)”}”(hX   Instead of win_req_t, drivers are now requested to fill out
`struct pcmcia_device *p_dev->resource[2,3,4,5]` for up to four ioport
ranges. After a call to pcmcia_request_window(), the regions found there
are reserved and may be used immediately -- until pcmcia_release_window()
is called.”h]”(hŒ<Instead of win_req_t, drivers are now requested to fill out
”…””}”(hj  hžhhŸNh Nubhû)”}”(hŒ0`struct pcmcia_device *p_dev->resource[2,3,4,5]`”h]”hŒ.struct pcmcia_device *p_dev->resource[2,3,4,5]”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1húhj  ubhŒ´ for up to four ioport
ranges. After a call to pcmcia_request_window(), the regions found there
are reserved and may be used immediately -- until pcmcia_release_window()
is called.”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj   ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Khjý  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjù  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX<  pcmcia_request_io changes (as of 2.6.36)
 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.
”h]”hÓ)”}”(hhh]”hØ)”}”(hX7  pcmcia_request_io changes (as of 2.6.36)
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.
”h]”(hÞ)”}”(hŒ(pcmcia_request_io changes (as of 2.6.36)”h]”hŒ(pcmcia_request_io changes (as of 2.6.36)”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K&hjT  ubhî)”}”(hhh]”h¸)”}”(hX  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.”h]”(hŒ;Instead of io_req_t, drivers are now requested to fill out
”…””}”(hji  hžhhŸNh Nubhû)”}”(hŒ,`struct pcmcia_device *p_dev->resource[0,1]`”h]”hŒ*struct pcmcia_device *p_dev->resource[0,1]”…””}”(hjq  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1húhji  ubhŒ¦ 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.”…””}”(hji  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K"hjf  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjT  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K&hjQ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjM  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒËNo dev_info_t, no cs_types.h (as of 2.6.36)
 dev_info_t and a few other typedefs are removed. No longer use them
 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
 this file is gone.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒÈNo dev_info_t, no cs_types.h (as of 2.6.36)
dev_info_t and a few other typedefs are removed. No longer use them
in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
this file is gone.
”h]”(hÞ)”}”(hŒ+No dev_info_t, no cs_types.h (as of 2.6.36)”h]”hŒ+No dev_info_t, no cs_types.h (as of 2.6.36)”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K+hj¨  ubhî)”}”(hhh]”h¸)”}”(hŒ›dev_info_t and a few other typedefs are removed. No longer use them
in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
this file is gone.”h]”hŒ›dev_info_t and a few other typedefs are removed. No longer use them
in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
this file is gone.”…””}”(hj½  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K)hjº  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj¨  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K+hj¥  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj¡  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒZNo dev_node_t (as of 2.6.35)
 There is no more need to fill out a "dev_node_t" structure.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒYNo dev_node_t (as of 2.6.35)
There is no more need to fill out a "dev_node_t" structure.
”h]”(hÞ)”}”(hŒNo dev_node_t (as of 2.6.35)”h]”hŒNo dev_node_t (as of 2.6.35)”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K.hjê  ubhî)”}”(hhh]”h¸)”}”(hŒ;There is no more need to fill out a "dev_node_t" structure.”h]”hŒ?There is no more need to fill out a â€œdev_node_tâ€ structure.”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K.hjü  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjê  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K.hjç  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjã  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX\  New IRQ request rules (as of 2.6.35)
 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.
”h]”hÓ)”}”(hhh]”hØ)”}”(hXV  New IRQ request rules (as of 2.6.35)
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.
”h]”(hÞ)”}”(hŒ$New IRQ request rules (as of 2.6.35)”h]”hŒ$New IRQ request rules (as of 2.6.35)”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K7hj,  ubhî)”}”(hhh]”(h¸)”}”(hŒRInstead of the old pcmcia_request_irq() interface, drivers may now
choose between:”h]”hŒRInstead of the old pcmcia_request_irq() interface, drivers may now
choose between:”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K1hj>  ubhÈ)”}”(hhh]”(hÍ)”}”(hŒFcalling request_irq/free_irq directly. Use the IRQ from `*p_dev->irq`.”h]”h¸)”}”(hjT  h]”(hŒ8calling request_irq/free_irq directly. Use the IRQ from ”…””}”(hjV  hžhhŸNh Nubhû)”}”(hŒ`*p_dev->irq`”h]”hŒ*p_dev->irq”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1húhjV  ubhŒ.”…””}”(hjV  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K4hjR  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjO  ubhÍ)”}”(hŒŽuse pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
clean up automatically on calls to pcmcia_disable_device() or
device ejection.
”h]”h¸)”}”(hŒuse pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
clean up automatically on calls to pcmcia_disable_device() or
device ejection.”h]”hŒuse pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
clean up automatically on calls to pcmcia_disable_device() or
device ejection.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K5hj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhjO  ubeh}”(h]”h ]”h"]”h$]”h&]”j—  j˜  uh1hÇhŸh¶h K4hj>  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1híhj,  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K7hj)  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj%  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒöno cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
 Instead of the cs_error() callback or the CS_CHECK() macro, please use
 Linux-style checking of return values, and -- if necessary -- debug
 messages using "dev_dbg()" or "pr_debug()".
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒóno cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
Instead of the cs_error() callback or the CS_CHECK() macro, please use
Linux-style checking of return values, and -- if necessary -- debug
messages using "dev_dbg()" or "pr_debug()".
”h]”(hÞ)”}”(hŒ;no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)”h]”hŒ;no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K<hj¸  ubhî)”}”(hhh]”h¸)”}”(hŒ¶Instead of the cs_error() callback or the CS_CHECK() macro, please use
Linux-style checking of return values, and -- if necessary -- debug
messages using "dev_dbg()" or "pr_debug()".”h]”hŒ¾Instead of the cs_error() callback or the CS_CHECK() macro, please use
Linux-style checking of return values, and -- if necessary -- debug
messages using â€œdev_dbg()â€ or â€œpr_debug()â€.”…””}”(hjÍ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K:hjÊ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj¸  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K<hjµ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX}  New CIS tuple access (as of 2.6.33)
 Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
 pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
 only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
 interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
 a new helper "pcmcia_get_mac_from_cis()" was added.
”h]”hÓ)”}”(hhh]”hØ)”}”(hXx  New CIS tuple access (as of 2.6.33)
Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
a new helper "pcmcia_get_mac_from_cis()" was added.
”h]”(hÞ)”}”(hŒ#New CIS tuple access (as of 2.6.33)”h]”hŒ#New CIS tuple access (as of 2.6.33)”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h KChjú  ubhî)”}”(hhh]”h¸)”}”(hXS  Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
a new helper "pcmcia_get_mac_from_cis()" was added.”h]”hX_  Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
pcmcia_parse_tuple(), a driver shall use â€œpcmcia_get_tuple()â€ if it is
only interested in one (raw) tuple, or â€œpcmcia_loop_tuple()â€ if it is
interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
a new helper â€œpcmcia_get_mac_from_cis()â€ was added.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K?hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjú  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KChj÷  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjó  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX9  New configuration loop helper (as of 2.6.28)
 By calling pcmcia_loop_config(), a driver can iterate over all available
 configuration options. During a driver's probe() phase, one doesn't need
 to use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data and
 pcmcia_parse_tuple directly in most if not all cases.
”h]”hÓ)”}”(hhh]”hØ)”}”(hX5  New configuration loop helper (as of 2.6.28)
By calling pcmcia_loop_config(), a driver can iterate over all available
configuration options. During a driver's probe() phase, one doesn't need
to use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data and
pcmcia_parse_tuple directly in most if not all cases.
”h]”(hÞ)”}”(hŒ,New configuration loop helper (as of 2.6.28)”h]”hŒ,New configuration loop helper (as of 2.6.28)”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h KIhj<  ubhî)”}”(hhh]”h¸)”}”(hX  By calling pcmcia_loop_config(), a driver can iterate over all available
configuration options. During a driver's probe() phase, one doesn't need
to use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data and
pcmcia_parse_tuple directly in most if not all cases.”h]”hX  By calling pcmcia_loop_config(), a driver can iterate over all available
configuration options. During a driverâ€™s probe() phase, one doesnâ€™t need
to use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data and
pcmcia_parse_tuple directly in most if not all cases.”…””}”(hjQ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KFhjN  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj<  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KIhj9  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj5  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX  New release helper (as of 2.6.17)
 Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
 necessary now is calling pcmcia_disable_device. As there is no valid
 reason left to call pcmcia_release_io and pcmcia_release_irq, the
 exports for them were removed.
”h]”hÓ)”}”(hhh]”hØ)”}”(hX  New release helper (as of 2.6.17)
Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
necessary now is calling pcmcia_disable_device. As there is no valid
reason left to call pcmcia_release_io and pcmcia_release_irq, the
exports for them were removed.
”h]”(hÞ)”}”(hŒ!New release helper (as of 2.6.17)”h]”hŒ!New release helper (as of 2.6.17)”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h KOhj~  ubhî)”}”(hhh]”h¸)”}”(hŒîInstead of calling pcmcia_release_{configuration,io,irq,win}, all that's
necessary now is calling pcmcia_disable_device. As there is no valid
reason left to call pcmcia_release_io and pcmcia_release_irq, the
exports for them were removed.”h]”hŒðInstead of calling pcmcia_release_{configuration,io,irq,win}, all thatâ€™s
necessary now is calling pcmcia_disable_device. As there is no valid
reason left to call pcmcia_release_io and pcmcia_release_irq, the
exports for them were removed.”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KLhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj~  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KOhj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒÐUnify detach and REMOVAL event code, as well as attach and INSERTION
code (as of 2.6.16)::

     void (*remove)          (struct pcmcia_device *dev);
     int (*probe)            (struct pcmcia_device *dev);
”h]”(h¸)”}”(hŒZUnify detach and REMOVAL event code, as well as attach and INSERTION
code (as of 2.6.16)::”h]”hŒYUnify detach and REMOVAL event code, as well as attach and INSERTION
code (as of 2.6.16):”…””}”(hj½  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KQhj¹  ubhŒliteral_block”“”)”}”(hŒivoid (*remove)          (struct pcmcia_device *dev);
int (*probe)            (struct pcmcia_device *dev);”h]”hŒivoid (*remove)          (struct pcmcia_device *dev);
int (*probe)            (struct pcmcia_device *dev);”…””}”hjÍ  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jË  hŸh¶h KThj¹  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hX3  Move suspend, resume and reset out of event handler (as of 2.6.16)::

     int (*suspend)          (struct pcmcia_device *dev);
     int (*resume)           (struct pcmcia_device *dev);

should be initialized in struct pcmcia_driver, and handle
(SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events
”h]”(h¸)”}”(hŒDMove suspend, resume and reset out of event handler (as of 2.6.16)::”h]”hŒCMove suspend, resume and reset out of event handler (as of 2.6.16):”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KWhjã  ubjÌ  )”}”(hŒiint (*suspend)          (struct pcmcia_device *dev);
int (*resume)           (struct pcmcia_device *dev);”h]”hŒiint (*suspend)          (struct pcmcia_device *dev);
int (*resume)           (struct pcmcia_device *dev);”…””}”hjõ  sbah}”(h]”h ]”h"]”h$]”h&]”jÛ  jÜ  uh1jË  hŸh¶h KYhjã  ubh¸)”}”(hŒwshould be initialized in struct pcmcia_driver, and handle
(SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events”h]”hŒwshould be initialized in struct pcmcia_driver, and handle
(SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K\hjã  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hŒÉevent handler initialization in struct pcmcia_driver (as of 2.6.13)
 The event handler is notified of all events, and must be initialized
 as the event() callback in the driver's struct pcmcia_driver.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒÇevent handler initialization in struct pcmcia_driver (as of 2.6.13)
The event handler is notified of all events, and must be initialized
as the event() callback in the driver's struct pcmcia_driver.
”h]”(hÞ)”}”(hŒCevent handler initialization in struct pcmcia_driver (as of 2.6.13)”h]”hŒCevent handler initialization in struct pcmcia_driver (as of 2.6.13)”…””}”(hj"  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kahj  ubhî)”}”(hhh]”h¸)”}”(hŒ‚The event handler is notified of all events, and must be initialized
as the event() callback in the driver's struct pcmcia_driver.”h]”hŒ„The event handler is notified of all events, and must be initialized
as the event() callback in the driverâ€™s struct pcmcia_driver.”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K`hj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kahj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒZpcmcia/version.h should not be used (as of 2.6.13)
 This file will be removed eventually.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒYpcmcia/version.h should not be used (as of 2.6.13)
This file will be removed eventually.
”h]”(hÞ)”}”(hŒ2pcmcia/version.h should not be used (as of 2.6.13)”h]”hŒ2pcmcia/version.h should not be used (as of 2.6.13)”…””}”(hjd  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kdhj`  ubhî)”}”(hhh]”h¸)”}”(hŒ%This file will be removed eventually.”h]”hŒ%This file will be removed eventually.”…””}”(hju  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kdhjr  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj`  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kdhj]  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjY  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒ£in-kernel device<->driver matching (as of 2.6.13)
 PCMCIA devices and their correct drivers can now be matched in
 kernelspace. See 'devicetable.txt' for details.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒ¡in-kernel device<->driver matching (as of 2.6.13)
PCMCIA devices and their correct drivers can now be matched in
kernelspace. See 'devicetable.txt' for details.
”h]”(hÞ)”}”(hŒ1in-kernel device<->driver matching (as of 2.6.13)”h]”hŒ1in-kernel device<->driver matching (as of 2.6.13)”…””}”(hj¦  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Khhj¢  ubhî)”}”(hhh]”h¸)”}”(hŒnPCMCIA devices and their correct drivers can now be matched in
kernelspace. See 'devicetable.txt' for details.”h]”hŒrPCMCIA devices and their correct drivers can now be matched in
kernelspace. See â€˜devicetable.txtâ€™ for details.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kghj´  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj¢  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KhhjŸ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj›  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒÈDevice model integration (as of 2.6.11)
 A struct pcmcia_device is registered with the device model core,
 and can be used (e.g. for SET_NETDEV_DEV) by using
 handle_to_dev(client_handle_t * handle).
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒÅDevice model integration (as of 2.6.11)
A struct pcmcia_device is registered with the device model core,
and can be used (e.g. for SET_NETDEV_DEV) by using
handle_to_dev(client_handle_t * handle).
”h]”(hÞ)”}”(hŒ'Device model integration (as of 2.6.11)”h]”hŒ'Device model integration (as of 2.6.11)”…””}”(hjè  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kmhjä  ubhî)”}”(hhh]”h¸)”}”(hŒœA struct pcmcia_device is registered with the device model core,
and can be used (e.g. for SET_NETDEV_DEV) by using
handle_to_dev(client_handle_t * handle).”h]”hŒœA struct pcmcia_device is registered with the device model core,
and can be used (e.g. for SET_NETDEV_DEV) by using
handle_to_dev(client_handle_t * handle).”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kkhjö  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjä  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kmhjá  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjÝ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒˆConvert internal I/O port addresses to unsigned int (as of 2.6.11)
 ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒ‡Convert internal I/O port addresses to unsigned int (as of 2.6.11)
ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.
”h]”(hÞ)”}”(hŒBConvert internal I/O port addresses to unsigned int (as of 2.6.11)”h]”hŒBConvert internal I/O port addresses to unsigned int (as of 2.6.11)”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kphj&  ubhî)”}”(hhh]”h¸)”}”(hŒCioaddr_t should be replaced by unsigned int in PCMCIA card drivers.”h]”hŒCioaddr_t should be replaced by unsigned int in PCMCIA card drivers.”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kphj8  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj&  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kphj#  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX  irq_mask and irq_list parameters (as of 2.6.11)
 The irq_mask and irq_list parameters should no longer be used in
 PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
 determine which IRQ should be used. Therefore, link->irq.IRQInfo2
 is ignored.
”h]”hÓ)”}”(hhh]”hØ)”}”(hX  irq_mask and irq_list parameters (as of 2.6.11)
The irq_mask and irq_list parameters should no longer be used in
PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
determine which IRQ should be used. Therefore, link->irq.IRQInfo2
is ignored.
”h]”(hÞ)”}”(hŒ/irq_mask and irq_list parameters (as of 2.6.11)”h]”hŒ/irq_mask and irq_list parameters (as of 2.6.11)”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kvhjh  ubhî)”}”(hhh]”h¸)”}”(hŒÐThe irq_mask and irq_list parameters should no longer be used in
PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
determine which IRQ should be used. Therefore, link->irq.IRQInfo2
is ignored.”h]”hŒÐThe irq_mask and irq_list parameters should no longer be used in
PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
determine which IRQ should be used. Therefore, link->irq.IRQInfo2
is ignored.”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kshjz  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjh  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kvhje  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhja  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒ\client->PendingEvents is gone (as of 2.6.11)
 client->PendingEvents is no longer available.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒ[client->PendingEvents is gone (as of 2.6.11)
client->PendingEvents is no longer available.
”h]”(hÞ)”}”(hŒ,client->PendingEvents is gone (as of 2.6.11)”h]”hŒ,client->PendingEvents is gone (as of 2.6.11)”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Kyhjª  ubhî)”}”(hhh]”h¸)”}”(hŒ-client->PendingEvents is no longer available.”h]”hŒ-client->PendingEvents is no longer available.”…””}”(hj¿  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kyhj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjª  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kyhj§  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj£  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒ€client->Attributes are gone (as of 2.6.11)
 client->Attributes is unused, therefore it is removed from all
 PCMCIA card drivers
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒ~client->Attributes are gone (as of 2.6.11)
client->Attributes is unused, therefore it is removed from all
PCMCIA card drivers
”h]”(hÞ)”}”(hŒ*client->Attributes are gone (as of 2.6.11)”h]”hŒ*client->Attributes are gone (as of 2.6.11)”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K}hjì  ubhî)”}”(hhh]”h¸)”}”(hŒRclient->Attributes is unused, therefore it is removed from all
PCMCIA card drivers”h]”hŒRclient->Attributes is unused, therefore it is removed from all
PCMCIA card drivers”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K|hjþ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjì  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K}hjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjå  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hX˜  core functions no longer available (as of 2.6.11)
 The following functions have been removed from the kernel source
 because they are unused by all in-kernel drivers, and no external
 driver was reported to rely on them::

      pcmcia_get_first_region()
      pcmcia_get_next_region()
      pcmcia_modify_window()
      pcmcia_set_event_mask()
      pcmcia_get_first_window()
      pcmcia_get_next_window()
”h]”hÓ)”}”(hhh]”hØ)”}”(hX  core functions no longer available (as of 2.6.11)
The following functions have been removed from the kernel source
because they are unused by all in-kernel drivers, and no external
driver was reported to rely on them::

     pcmcia_get_first_region()
     pcmcia_get_next_region()
     pcmcia_modify_window()
     pcmcia_set_event_mask()
     pcmcia_get_first_window()
     pcmcia_get_next_window()
”h]”(hÞ)”}”(hŒ1core functions no longer available (as of 2.6.11)”h]”hŒ1core functions no longer available (as of 2.6.11)”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K‰hj.  ubhî)”}”(hhh]”(h¸)”}”(hŒ¨The following functions have been removed from the kernel source
because they are unused by all in-kernel drivers, and no external
driver was reported to rely on them::”h]”hŒ§The following functions have been removed from the kernel source
because they are unused by all in-kernel drivers, and no external
driver was reported to rely on them:”…””}”(hjC  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K€hj@  ubjÌ  )”}”(hŒ”pcmcia_get_first_region()
pcmcia_get_next_region()
pcmcia_modify_window()
pcmcia_set_event_mask()
pcmcia_get_first_window()
pcmcia_get_next_window()”h]”hŒ”pcmcia_get_first_region()
pcmcia_get_next_region()
pcmcia_modify_window()
pcmcia_set_event_mask()
pcmcia_get_first_window()
pcmcia_get_next_window()”…””}”hjQ  sbah}”(h]”h ]”h"]”h$]”h&]”jÛ  jÜ  uh1jË  hŸh¶h K„hj@  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1híhj.  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K‰hj+  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj'  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒ»device list iteration upon module removal (as of 2.6.10)
 It is no longer necessary to iterate on the driver's internal
 client list and call the ->detach() function upon module removal.
”h]”hÓ)”}”(hhh]”hØ)”}”(hŒ¹device list iteration upon module removal (as of 2.6.10)
It is no longer necessary to iterate on the driver's internal
client list and call the ->detach() function upon module removal.
”h]”(hÞ)”}”(hŒ8device list iteration upon module removal (as of 2.6.10)”h]”hŒ8device list iteration upon module removal (as of 2.6.10)”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h Khj~  ubhî)”}”(hhh]”h¸)”}”(hŒIt is no longer necessary to iterate on the driver's internal
client list and call the ->detach() function upon module removal.”h]”hŒIt is no longer necessary to iterate on the driverâ€™s internal
client list and call the ->detach() function upon module removal.”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŒhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhj~  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Khj{  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhjw  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hXù  Resource management. (as of 2.6.8)
 Although the PCMCIA subsystem will allocate resources for cards,
 it no longer marks these resources busy. This means that driver
 authors are now responsible for claiming your resources as per
 other drivers in Linux. You should use request_region() to mark
 your IO regions in-use, and request_mem_region() to mark your
 memory regions in-use. The name argument should be a pointer to
 your driver name. Eg, for pcnet_cs, name should point to the
 string "pcnet_cs".
”h]”hÓ)”}”(hhh]”hØ)”}”(hXñ  Resource management. (as of 2.6.8)
Although the PCMCIA subsystem will allocate resources for cards,
it no longer marks these resources busy. This means that driver
authors are now responsible for claiming your resources as per
other drivers in Linux. You should use request_region() to mark
your IO regions in-use, and request_mem_region() to mark your
memory regions in-use. The name argument should be a pointer to
your driver name. Eg, for pcnet_cs, name should point to the
string "pcnet_cs".
”h]”(hÞ)”}”(hŒ"Resource management. (as of 2.6.8)”h]”hŒ"Resource management. (as of 2.6.8)”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhŸh¶h K—hjÀ  ubhî)”}”(hhh]”h¸)”}”(hXÍ  Although the PCMCIA subsystem will allocate resources for cards,
it no longer marks these resources busy. This means that driver
authors are now responsible for claiming your resources as per
other drivers in Linux. You should use request_region() to mark
your IO regions in-use, and request_mem_region() to mark your
memory regions in-use. The name argument should be a pointer to
your driver name. Eg, for pcnet_cs, name should point to the
string "pcnet_cs".”h]”hXÑ  Although the PCMCIA subsystem will allocate resources for cards,
it no longer marks these resources busy. This means that driver
authors are now responsible for claiming your resources as per
other drivers in Linux. You should use request_region() to mark
your IO regions in-use, and request_mem_region() to mark your
memory regions in-use. The name argument should be a pointer to
your driver name. Eg, for pcnet_cs, name should point to the
string â€œpcnet_csâ€.”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhjÒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híhjÀ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K—hj½  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÒhj¹  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸNh NubhÍ)”}”(hŒéCardServices is gone
CardServices() in 2.4 is just a big switch statement to call various
services.  In 2.6, all of those entry points are exported and called
directly (except for pcmcia_report_error(), just use cs_error() instead).
”h]”h¸)”}”(hŒèCardServices is gone
CardServices() in 2.4 is just a big switch statement to call various
services.  In 2.6, all of those entry points are exported and called
directly (except for pcmcia_report_error(), just use cs_error() instead).”h]”hŒèCardServices is gone
CardServices() in 2.4 is just a big switch statement to call various
services.  In 2.6, all of those entry points are exported and called
directly (except for pcmcia_report_error(), just use cs_error() instead).”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K™hjû  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h NubhÍ)”}”(hŒ€struct pcmcia_driver
You need to use struct pcmcia_driver and pcmcia_{un,}register_driver
instead of {un,}register_pccard_driver”h]”h¸)”}”(hŒ€struct pcmcia_driver
You need to use struct pcmcia_driver and pcmcia_{un,}register_driver
instead of {un,}register_pccard_driver”h]”hŒ€struct pcmcia_driver
You need to use struct pcmcia_driver and pcmcia_{un,}register_driver
instead of {un,}register_pccard_driver”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kžhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÌhhÉhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”j—  Œ*”uh1hÇhŸh¶h Khh£hžhubeh}”(h]”Œdriver-changes”ah ]”h"]”Œdriver changes”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j]  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”j7  j4  sŒ	nametypes”}”j7  ‰sh}”j4  h£sŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.