Lines Matching +full:as +full:- +full:is
7 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
8 If `struct pcmcia_device *p_dev->config_flags` is set accordingly,
14 - CONF_AUTO_CHECK_VCC : check for matching Vcc
15 - CONF_AUTO_SET_VPP : set Vpp
16 - CONF_AUTO_AUDIO : auto-enable audio line, if required
17 - CONF_AUTO_SET_IO : set ioport resources (->resource[0,1])
18 - CONF_AUTO_SET_IOMEM : set first iomem resource (->resource[2])
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
22 as it mirrors pcmcia_disable_device(). Configuration settings are now
26 * pcmcia_request_window changes (as of 2.6.36)
28 `struct pcmcia_device *p_dev->resource[2,3,4,5]` for up to four ioport
30 are reserved and may be used immediately -- until pcmcia_release_window()
31 is called.
33 * pcmcia_request_io changes (as of 2.6.36)
35 `struct pcmcia_device *p_dev->resource[0,1]` for up to two ioport
40 * No dev_info_t, no cs_types.h (as of 2.6.36)
42 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
43 this file is gone.
45 * No dev_node_t (as of 2.6.35)
46 There is no more need to fill out a "dev_node_t" structure.
48 * New IRQ request rules (as of 2.6.35)
52 - calling request_irq/free_irq directly. Use the IRQ from `*p_dev->irq`.
53 - use pcmcia_request_irq(p_dev, handler_t); the PCMCIA core will
57 * no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
59 Linux-style checking of return values, and -- if necessary -- debug
62 * New CIS tuple access (as of 2.6.33)
64 pcmcia_parse_tuple(), a driver shall use "pcmcia_get_tuple()" if it is
65 only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
69 * New configuration loop helper (as of 2.6.28)
75 * New release helper (as of 2.6.17)
77 necessary now is calling pcmcia_disable_device. As there is no valid
81 * Unify detach and REMOVAL event code, as well as attach and INSERTION
82 code (as of 2.6.16)::
87 * Move suspend, resume and reset out of event handler (as of 2.6.16)::
95 * event handler initialization in struct pcmcia_driver (as of 2.6.13)
96 The event handler is notified of all events, and must be initialized
97 as the event() callback in the driver's struct pcmcia_driver.
99 * pcmcia/version.h should not be used (as of 2.6.13)
102 * in-kernel device<->driver matching (as of 2.6.13)
106 * Device model integration (as of 2.6.11)
107 A struct pcmcia_device is registered with the device model core,
111 * Convert internal I/O port addresses to unsigned int (as of 2.6.11)
114 * irq_mask and irq_list parameters (as of 2.6.11)
116 PCMCIA card drivers. Instead, it is the job of the PCMCIA core to
117 determine which IRQ should be used. Therefore, link->irq.IRQInfo2
118 is ignored.
120 * client->PendingEvents is gone (as of 2.6.11)
121 client->PendingEvents is no longer available.
123 * client->Attributes are gone (as of 2.6.11)
124 client->Attributes is unused, therefore it is removed from all
127 * core functions no longer available (as of 2.6.11)
129 because they are unused by all in-kernel drivers, and no external
139 * device list iteration upon module removal (as of 2.6.10)
140 It is no longer necessary to iterate on the driver's internal
141 client list and call the ->detach() function upon module removal.
143 * Resource management. (as of 2.6.8)
146 authors are now responsible for claiming your resources as per
148 your IO regions in-use, and request_mem_region() to mark your
149 memory regions in-use. The name argument should be a pointer to
153 * CardServices is gone
154 CardServices() in 2.4 is just a big switch statement to call various