Lines Matching refs:platform
7 may be configured and combined in different ways to meet the needs of platform integrators who
32 hexagonal cell with the application on the inside and the platform on the outside.
45 * Use a service/device provided by the platform or environment.
100 - | A specific set of hardware drivers and target platform specific settings.
101 | A platform definition may depend on:
123 that uses flash storage emulated with semihosting on the AEM FVP platform), use::
132 - Set TS_PLATFORM to n1sdp platform name
140 likely to grow to accommodate platform variability and different tradeoffs for how the infrastructu…
168 The Trusted Services project is not intended to be a home for platform specific code such as
169 device drivers. Ideally, device drivers and other platform specific code should be reused
173 an external project is not possible, the platform directory structure can accommodate driver
181 All files related to supporting different platforms reside beneath the platform top-level
186 Within the TS project, a platform provider is responsible for adding and maintaining the
187 glue that enables platform specific code to be used from a particular source. The platform
193 Each platform provider is represented by a subdirectory beneath ``platform/providers``. For
196 platform
203 |-- platform.cmake
205 Under each platform leaf directory is a file called ``platform.cmake``. This file implements
207 process. How this interface is realized is entirely down to the platform provider. An
209 selection. Any additional files needed to support platform configuration and build may be
210 included within the platform provider's sub-tree.
213 be possible to override the default ``platform/providers`` directory path to allow an
217 Although the TS project structure doesn't mandate it, platform specific firmware is likely
220 vendors may reuse existing CI and project infrastructure for platform components that they
223 Platform support that depends on EDK2 platform components is represented by the edk2 platform
224 provider. Files related to the EDK2 platform provider are organized as follows::
226 platform
230 … |- platform - Directory for platform definitions, organized by contributor
233 |- platform.cmake
245 …- | A platform that never provides any drivers. The ``ts/vanilla`` platform should be used when an…
246 …| device framework and no additional drivers need to be provided by the platform. An attempt to bu…
247 …| platform dependencies on the vanilla platform will result in a build-time error. The vanilla pla…
248 | default at build-time if no explicit platform has been specified.
250 …- | A platform that provides a complete set of drivers that may be selected when building any depl…
251 …that don't offer functionality suitable for production builds. The mock platform is useful for CI …
252 …| testing of deployments with platform dependencies. You should always expect a deployment with pl…
257 Alternative driver models are represented by subdirectories beneath ``platform/driver_model``.
265 platform
272 with driver code imported from edk2-platforms, sub-directories beneath platform/driver_model/edk2
276 platform
293 upstream repo or will live under the ``platform/drivers`` parent.