1This file details changes in 2.6 which affect PCMCIA card driver authors:
2* pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
3   If struct pcmcia_device *p_dev->config_flags is set accordingly,
4   pcmcia_loop_config() now sets up certain configuration values
5   automatically, though the driver may still override the settings
6   in the callback function. The following autoconfiguration options
7   are provided at the moment:
8	CONF_AUTO_CHECK_VCC : check for matching Vcc
9	CONF_AUTO_SET_VPP   : set Vpp
10	CONF_AUTO_AUDIO     : auto-enable audio line, if required
11	CONF_AUTO_SET_IO    : set ioport resources (->resource[0,1])
12	CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
13
14* pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
15   pcmcia_request_configuration() got renamed to pcmcia_enable_device(),
16   as it mirrors pcmcia_disable_device(). Configuration settings are now
17   stored in struct pcmcia_device, e.g. in the fields config_flags,
18   config_index, config_base, vpp.
19
20* pcmcia_request_window changes (as of 2.6.36)
21   Instead of win_req_t, drivers are now requested to fill out
22   struct pcmcia_device *p_dev->resource[2,3,4,5] for up to four ioport
23   ranges. After a call to pcmcia_request_window(), the regions found there
24   are reserved and may be used immediately -- until pcmcia_release_window()
25   is called.
26
27* pcmcia_request_io changes (as of 2.6.36)
28   Instead of io_req_t, drivers are now requested to fill out
29   struct pcmcia_device *p_dev->resource[0,1] for up to two ioport
30   ranges. After a call to pcmcia_request_io(), the ports found there
31   are reserved, after calling pcmcia_request_configuration(), they may
32   be used.
33
34* No dev_info_t, no cs_types.h (as of 2.6.36)
35   dev_info_t and a few other typedefs are removed. No longer use them
36   in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
37   this file is gone.
38
39* No dev_node_t (as of 2.6.35)
40   There is no more need to fill out a "dev_node_t" structure.
41
42* New IRQ request rules (as of 2.6.35)
43   Instead of the old pcmcia_request_irq() interface, drivers may now
44   choose between:
45   - calling request_irq/free_irq directly. Use the IRQ from *p_dev->irq.
46   - use pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
47     clean up automatically on calls to pcmcia_disable_device() or
48     device ejection.
49
50* no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
51   Instead of the cs_error() callback or the CS_CHECK() macro, please use
52   Linux-style checking of return values, and -- if necessary -- debug
53   messages using "dev_dbg()" or "pr_debug()".
54
55* New CIS tuple access (as of 2.6.33)
56   Instead of pcmcia_get_{first,next}_tuple(), pcmcia_get_tuple_data() and
57   pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
58   only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
59   interested in all tuples of one type. To decode the MAC from CISTPL_FUNCE,
60   a new helper "pcmcia_get_mac_from_cis()" was added.
61
62* New configuration loop helper (as of 2.6.28)
63   By calling pcmcia_loop_config(), a driver can iterate over all available
64   configuration options. During a driver's probe() phase, one doesn't need
65   to use pcmcia_get_{first,next}_tuple, pcmcia_get_tuple_data and
66   pcmcia_parse_tuple directly in most if not all cases.
67
68* New release helper (as of 2.6.17)
69   Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
70   necessary now is calling pcmcia_disable_device. As there is no valid
71   reason left to call pcmcia_release_io and pcmcia_release_irq, the
72   exports for them were removed.
73
74* Unify detach and REMOVAL event code, as well as attach and INSERTION
75  code (as of 2.6.16)
76       void (*remove)          (struct pcmcia_device *dev);
77       int (*probe)            (struct pcmcia_device *dev);
78
79* Move suspend, resume and reset out of event handler (as of 2.6.16)
80       int (*suspend)          (struct pcmcia_device *dev);
81       int (*resume)           (struct pcmcia_device *dev);
82  should be initialized in struct pcmcia_driver, and handle
83  (SUSPEND == RESET_PHYSICAL) and (RESUME == CARD_RESET) events
84
85* event handler initialization in struct pcmcia_driver (as of 2.6.13)
86   The event handler is notified of all events, and must be initialized
87   as the event() callback in the driver's struct pcmcia_driver.
88
89* pcmcia/version.h should not be used (as of 2.6.13)
90   This file will be removed eventually.
91
92* in-kernel device<->driver matching (as of 2.6.13)
93   PCMCIA devices and their correct drivers can now be matched in
94   kernelspace. See 'devicetable.txt' for details.
95
96* Device model integration (as of 2.6.11)
97   A struct pcmcia_device is registered with the device model core,
98   and can be used (e.g. for SET_NETDEV_DEV) by using
99   handle_to_dev(client_handle_t * handle).
100
101* Convert internal I/O port addresses to unsigned int (as of 2.6.11)
102   ioaddr_t should be replaced by unsigned int in PCMCIA card drivers.
103
104* irq_mask and irq_list parameters (as of 2.6.11)
105   The irq_mask and irq_list parameters should no longer be used in
106   PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
107   determine which IRQ should be used. Therefore, link->irq.IRQInfo2
108   is ignored.
109
110* client->PendingEvents is gone (as of 2.6.11)
111   client->PendingEvents is no longer available.
112
113* client->Attributes are gone (as of 2.6.11)
114   client->Attributes is unused, therefore it is removed from all
115   PCMCIA card drivers
116
117* core functions no longer available (as of 2.6.11)
118   The following functions have been removed from the kernel source
119   because they are unused by all in-kernel drivers, and no external
120   driver was reported to rely on them:
121	pcmcia_get_first_region()
122	pcmcia_get_next_region()
123	pcmcia_modify_window()
124	pcmcia_set_event_mask()
125	pcmcia_get_first_window()
126	pcmcia_get_next_window()
127
128* device list iteration upon module removal (as of 2.6.10)
129   It is no longer necessary to iterate on the driver's internal
130   client list and call the ->detach() function upon module removal.
131
132* Resource management. (as of 2.6.8)
133   Although the PCMCIA subsystem will allocate resources for cards,
134   it no longer marks these resources busy. This means that driver
135   authors are now responsible for claiming your resources as per
136   other drivers in Linux. You should use request_region() to mark
137   your IO regions in-use, and request_mem_region() to mark your
138   memory regions in-use. The name argument should be a pointer to
139   your driver name. Eg, for pcnet_cs, name should point to the
140   string "pcnet_cs".
141
142* CardServices is gone
143  CardServices() in 2.4 is just a big switch statement to call various
144  services.  In 2.6, all of those entry points are exported and called
145  directly (except for pcmcia_report_error(), just use cs_error() instead).
146
147* struct pcmcia_driver
148  You need to use struct pcmcia_driver and pcmcia_{un,}register_driver
149  instead of {un,}register_pccard_driver
150