card_if.m revision 53855
1# 2# Copyright (c) 1999 M. Warner Losh. 3# All rights reserved. 4# 5# Redistribution and use in source and binary forms, with or without 6# modification, are permitted provided that the following conditions 7# are met: 8# 1. Redistributions of source code must retain the above copyright 9# notice, this list of conditions and the following disclaimer. 10# 2. Redistributions in binary form must reproduce the above copyright 11# notice, this list of conditions and the following disclaimer in the 12# documentation and/or other materials provided with the distribution. 13# 14# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 15# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 16# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 17# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 18# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 19# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 20# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 21# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 22# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 23# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 24# SUCH DAMAGE. 25# 26# $FreeBSD: head/sys/dev/pccard/card_if.m 53855 1999-11-28 21:11:13Z imp $ 27# 28 29INTERFACE card; 30 31# 32# Companion interface for pccard. We need to set attributes for memory 33# and i/o port mappings (as well as other types of attributes) that have 34# a well defined meaning inside the pccard/cardbus system. The bus 35# methods are inadequate for this because this must be done at the time the 36# resources are set for the device, which predates their activation. Also, 37# the driver activating the resources doesn't necessarily know or need to know 38# these attributes. 39# 40# XXX A nagging doubt in the back of my mind suggests that these sorts of 41# XXX things might be able to be done with ivars. This nagging doubt doesn't 42# XXX offer a good way to actually do this, but remains nonetheless. 43# 44METHOD int set_resource_attribute { 45 device_t dev; 46 device_t child; 47 int *rid; 48 u_int flags; 49}; 50 51METHOD int get_resource_attribute { 52 device_t dev; 53 device_t child; 54 int rid; 55 u_int *flags; 56}; 57