1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
32 33 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