57 lines
2.2 KiB
Mathematica
57 lines
2.2 KiB
Mathematica
|
#
|
||
|
|
# Copyright (c) 1999 M. Warner Losh.
|
||
|
|
# All rights reserved.
|
||
|
|
#
|
||
|
|
# Redistribution and use in source and binary forms, with or without
|
||
|
|
# modification, are permitted provided that the following conditions
|
||
|
|
# are met:
|
||
|
|
# 1. Redistributions of source code must retain the above copyright
|
||
|
|
# notice, this list of conditions and the following disclaimer.
|
||
|
|
# 2. Redistributions in binary form must reproduce the above copyright
|
||
|
|
# notice, this list of conditions and the following disclaimer in the
|
||
|
|
# documentation and/or other materials provided with the distribution.
|
||
|
|
#
|
||
|
|
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
||
|
|
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||
|
|
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||
|
|
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
||
|
|
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||
|
|
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||
|
|
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||
|
|
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||
|
|
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||
|
|
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||
|
|
# SUCH DAMAGE.
|
||
|
|
#
|
||
|
|
# $FreeBSD$
|
||
|
|
#
|
||
|
|
|
||
|
|
INTERFACE card;
|
||
|
|
|
||
|
|
#
|
||
|
|
# Companion interface for pccard. We need to set attributes for memory
|
||
|
|
# and i/o port mappings (as well as other types of attributes) that have
|
||
|
|
# a well defined meaning inside the pccard/cardbus system. The bus
|
||
|
|
# methods are inadequate for this because this must be done at the time the
|
||
|
|
# resources are set for the device, which predates their activation. Also,
|
||
|
|
# the driver activating the resources doesn't necessarily know or need to know
|
||
|
|
# these attributes.
|
||
|
|
#
|
||
|
|
# XXX A nagging doubt in the back of my mind suggests that these sorts of
|
||
|
|
# XXX things might be able to be done with ivars. This nagging doubt doesn't
|
||
|
|
# XXX offer a good way to actually do this, but remains nonetheless.
|
||
|
|
#
|
||
|
|
METHOD int set_resource_attribute {
|
||
|
|
device_t dev;
|
||
|
|
device_t child;
|
||
|
|
int *rid;
|
||
|
|
u_int flags;
|
||
|
|
};
|
||
|
|
|
||
|
|
METHOD int get_resource_attribute {
|
||
|
|
device_t dev;
|
||
|
|
device_t child;
|
||
|
|
int rid;
|
||
|
|
u_int *flags;
|
||
|
|
};
|