- 31 8月, 2008 1 次提交
-
-
由 Dominik Brodowski 提交于
16-bit PCMCIA device handling function definitions are moved to ds.h, internal definitions to cs_internal.h. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 23 8月, 2008 3 次提交
-
-
由 Dominik Brodowski 提交于
By passing the current Vcc setting to the pcmcia_config_loop callback function, we can remove pcmcia_get_configuration_info() calls from many drivers. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
由 Dominik Brodowski 提交于
Many drivers use the default CIS entry within their pcmcia_config_loop() callback function. Therefore, factor the default CIS entry handling out. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
由 Dominik Brodowski 提交于
By calling pcmcia_loop_config(), a pcmcia 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. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 03 8月, 2008 1 次提交
-
-
由 Dominik Brodowski 提交于
Instead of copying CIS override data in socket_sysfs.c or ds.c, and then again in cistpl.c, only do so once. Also, cisdump_t is now only used by the deprecated ioctl. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 24 6月, 2008 1 次提交
-
-
由 Dominik Brodowski 提交于
As cisinfo_t only contains one unsigned_int, pccard_validate_cis can be simplified by passing that around directly. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 31 3月, 2006 1 次提交
-
-
由 Dominik Brodowski 提交于
Remove the compatibility wrappers, as they can (now) also be implemented using macros. Please continue using these wrappers instead of new functions until a new API has stabilized. Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
-
- 17 4月, 2005 1 次提交
-
-
由 Linus Torvalds 提交于
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-