1 /*
2 * Copyright (c) 2012, Texas Instruments Incorporated
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 *
9 * * Redistributions of source code must retain the above copyright
10 * notice, this list of conditions and the following disclaimer.
11 *
12 * * Redistributions in binary form must reproduce the above copyright
13 * notice, this list of conditions and the following disclaimer in the
14 * documentation and/or other materials provided with the distribution.
15 *
16 * * Neither the name of Texas Instruments Incorporated nor the names of
17 * its contributors may be used to endorse or promote products derived
18 * from this software without specific prior written permission.
19 *
20 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
21 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
22 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
23 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
24 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
25 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
26 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
27 * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
28 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
29 * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
30 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
31 */
32 /*
33 * ======== package.xdc ========
34 *
35 */
36 requires ti.sysbios.interfaces;
37
38 /*!
39 * ======== ti.sysbios.family ========
40 * Contains family-specific modules for SYS/BIOS
41 *
42 * The ti.sysbios.family package contains family-specific implementations
43 * of modules in the Hardware Abstraction Layer
44 * ({@link ti.sysbios.hal HAL}) package.
45 *
46 * The SYS/BIOS ti.sysbios.hal
47 * package requires target/device-specific API
48 * implementations to achieve their functionality. To provide a common set
49 * of APIs for these modules across all supported families/devices, SYS/BIOS
50 * uses the RTSC proxy-delegate module mechanism. That is, the HAL
51 * modules serve as a proxies for a corresponding
52 * family-specific module implementation.
53 *
54 * The generic HAL APIs are designed to cover the great majority of use
55 * cases. If you are concerned with easy portability between
56 * different TI devices, you should use the generic HAL APIs as much
57 * as possible. However, if the generic APIs cannot enable use of a
58 * device-specific hardware feature that is advantageous to the software
59 * application, you may choose to use the target/device-specific APIs.
60 *
61 * During the configuration step of the application build, the
62 * modules in the ti.sysbios.hal package locate and bind
63 * themselves to appropriate delegate module implementations based on the
64 * current target
65 * and platform specified in your config.bld file. The delegate binding
66 * process is done internally.
67 *
68 * For example, if your config.bld file specifies that one of your build
69 * targets is the C64P family, the {@link ti.sysbios.hal.Hwi} knows to
70 * bind itself to the {@link ti.sysbios.family.c64p.Hwi} implementation.
71 *
72 * The {@link ./doc-files/delegates.html SYS/BIOS Delegates Usage} page
73 * lists the delegates available for every target and platform.
74 *
75 */
76 package ti.sysbios.family [2,0,0,0] {
77 module Settings;
78 }
79