1#
2# CDDL HEADER START
3#
4# The contents of this file are subject to the terms of the
5# Common Development and Distribution License, Version 1.0 only
6# (the "License").  You may not use this file except in compliance
7# with the License.
8#
9# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
10# or http://www.opensolaris.org/os/licensing.
11# See the License for the specific language governing permissions
12# and limitations under the License.
13#
14# When distributing Covered Code, include this CDDL HEADER in each
15# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
16# If applicable, add the following below this CDDL HEADER, with the
17# fields enclosed by brackets "[]" replaced with your own identifying
18# information: Portions Copyright [yyyy] [name of copyright owner]
19#
20# CDDL HEADER END
21#
22#
23# Copyright (c) 2000 by Sun Microsystems, Inc.
24# All rights reserved.
25#
26#ident	"%Z%%M%	%I%	%E% SMI"
27
28name="bofi" parent="pseudo";
29
30# The 'bofi-nexus' property specifies the name of the nexus where data accesses
31# are intercepted. This should be the name of the parent (or ancestor) nexus of
32# the driver(s) to be tested.
33#bofi-nexus="nexus_to_intercept";
34
35# The 'bofi-to-test' property identifies a list of drivers whose accesses
36# should be intercepted, or if each name is preceeded by the ! character a list
37# of drivers not to test. If any name is not preceeded by this character then
38# every name is assumed to be the name of a driver to test. If the property
39# value is undefined or the empty string then all drivers will be tested. 
40#bofi-to-test="driver_to_test1 driver_to_test2 ...";
41
42# The 'bofi-ddi-check' property may be set to "on" or "off".  The "on"
43# setting causes bofi to validate that the mapped address returned from
44# ddi_regs_map_setup(9F) is not used outside the context of DDI data
45# access calls.  When set to "off", no validation occurs.
46bofi-ddi-check="on";
47
48# The 'bofi-range-check' property may be set to "panic", "warn" or "off".
49# The "warn" and "panic" settings cause bofi to validate that requested data
50# access sizes are consistent with the access handle used to perform the data
51# access. The "warn" setting causes warning to be displayed on the system
52# console on misuse. The "panic" setting causes the system to panic on misuse.
53# When set to "off", no validation occurs.
54bofi-range-check="panic";
55
56# The 'bofi-sync-check' property may be set to "on" or "off".  The "on"
57# setting causes bofi to validate that the tested drivers are compliant with
58# respect the use of ddi_dma_sync(9F) calls. When set to "off", no validation
59# occurs.
60bofi-sync-check="on";
61