Home
last modified time | relevance | path

Searched refs:interface (Results 1 – 25 of 71) sorted by relevance

123

/lib/efi_selftest/
A Defi_selftest_manageprotocols.c20 struct interface { struct
36 static struct interface interface1; argument
37 static struct interface interface2;
38 static struct interface interface3;
39 static struct interface interface4;
138 struct interface *interface; in execute() local
149 ret = boottime->handle_protocol(handle1, &guid3, (void **)&interface); in execute()
154 if (interface != &interface3) { in execute()
158 ret = boottime->handle_protocol(handle1, &guid2, (void **)&interface); in execute()
281 ret = boottime->locate_protocol(&guid1, NULL, (void **)&interface); in execute()
[all …]
A Defi_selftest_register_notify.c18 struct interface { struct
127 struct interface *interface; in execute() local
128 struct interface interface1, interface2; in execute()
149 interface = NULL; in execute()
150 ret = boottime->open_protocol(handle1, &guid1, (void**)&interface, in execute()
157 if (interface != &interface1) { in execute()
202 interface = NULL; in execute()
203 ret = boottime->open_protocol(handle1, &guid1, (void**)&interface, in execute()
210 if (interface != &interface2) { in execute()
A Defi_selftest_open_protocol.c18 struct interface { struct
27 static struct interface interface1; argument
88 void *interface; in execute() local
94 ret = boottime->handle_protocol(handle1, &guid1, &interface); in execute()
99 if (interface != &interface1) { in execute()
120 ret = boottime->handle_protocol(handle1, &guid1, &interface); in execute()
148 ret = boottime->open_protocol(handle1, &guid1, &interface, in execute()
A Defi_selftest_devicepath.c19 struct interface { struct
21 } interface; variable
199 &interface); in setup()
215 &interface); in setup()
252 &interface); in teardown()
266 &interface); in teardown()
A Defi_selftest_controllers.c81 void *interface; in supported() local
85 &interface, handle_driver, in supported()
119 void *interface; in start() local
124 &interface, handle_driver, in start()
149 &interface, handle_child_controller[i], in start()
/lib/lwip/lwip/contrib/apps/LwipMibCompiler/Mibs/
A DIF-MIB99 than zero value used to identify an interface or interface
136 -- of a network interface is considered to be an interface.
153 particular interface."
206 interface hardware/software."
229 interface."
548 -- Extension to the interface table
840 for this interface.
1051 the (whole) interface stack. A change of the interface
1578 interface."
1600 interface's test."
[all …]
A DIP-MIB327 interface."
374 of the interface."
394 -- v6 interface table
430 interface."
476 interface address.
509 of the interface.
2988 interface."
3076 interface."
3368 this interface."
3380 this interface."
[all …]
A DRFC1213-MIB188 -- interfaces. Each interface is thought of as being
199 "A list of interface entries. The number of
210 interface."
283 of the hardware interface."
339 on the interface."
375 "The desired state of the interface. The
413 interface, including framing characters."
474 interface, including framing characters."
537 interface. For example, if the interface is
981 datagrams received on this interface."
[all …]
/lib/efi_driver/
A Defi_block_device.c121 efi_bl_create_block_device(efi_handle_t handle, void *interface) in efi_bl_create_block_device() argument
128 struct efi_block_io *io = interface; in efi_bl_create_block_device()
155 plat->io = interface; in efi_bl_create_block_device()
188 efi_handle_t handle, void *interface) in efi_bl_bind() argument
193 EFI_PRINT("%s: handle %p, interface %p\n", __func__, handle, interface); in efi_bl_bind()
195 if (!obj || !interface) in efi_bl_bind()
199 ret = efi_bl_create_block_device(handle, interface); in efi_bl_bind()
A Defi_uclass.c69 void *interface; in efi_uc_supported() local
87 &interface, this->driver_binding_handle, in efi_uc_supported()
125 void *interface = NULL; in efi_uc_start() local
135 &interface, this->driver_binding_handle, in efi_uc_start()
150 ret = bp->ops->bind(bp, controller_handle, interface); in efi_uc_start()
/lib/mbedtls/external/mbedtls/docs/architecture/testing/
A Ddriver-interface-test-strategy.md1 # Mbed TLS driver interface test strategy
7 ## Secure element driver interface testing
11 #### Opaque driver interface
13 The [unified driver interface](../../proposed/psa-driver-interface.md) supports both transparent dr…
17 #### Dynamic secure element driver interface
19 …driver interface (SE interface for short) is defined by [`psa/crypto_se_driver.h`](../../../includ…
23 ### SE driver interface unit tests
109 We should have at least one driver that covers the whole interface:
117 ## Transparent driver interface testing
119 The [unified driver interface](../../proposed/psa-driver-interface.md) defines interfaces for accel…
[all …]
/lib/mbedtls/external/mbedtls/docs/proposed/
A Dpsa-driver-developer-guide.md9 …rence of the interface between Mbed TLS and drivers, refer to the [PSA Cryptoprocessor Driver Inte…
11 The interface is not fully implemented in Mbed TLS yet. Please note that the interface may still ch…
17 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
28 …er description syntax”](psa-driver-interface.html#driver-description-syntax) of the PSA cryptograp…
38 …fied in the PSA Cryptography Driver Interface specification](psa-driver-interface.html#driver-entr…
A Dpsa-driver-integration-guide.md7 …d TLS with additional cryptoprocessor drivers that follow the PSA cryptoprocessor driver interface.
9 The interface is not fully implemented in Mbed TLS yet. Please note that the interface may still ch…
13 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
A Dpsa-conditional-inclusion-c.md4 …ument is a proposed interface for deciding at build time which cryptographic mechanisms to include…
12 …lication-programming-interface) specifies the interface between a PSA Cryptography implementation …
14 The present document proposes a way for an application using the PSA cryptography interface to decl…
22 In the PSA cryptography interface, the **core** (built-in implementations of cryptographic mechanis…
24 The current model is difficult to adapt to the PSA interface for several reasons. The `MBEDTLS_xxx_…
28 [Req.interface] The application can declare which cryptographic mechanisms it needs.
36 …tion of the PSA cryptography specifications and Mbed TLS. Therefore the interface must remain suff…
129 These symbols are not part of the public interface of Mbed TLS towards applications or to drivers, …
167 … application code or driver code, since they are not part of the public interface of the library. …
209 ### Open questions about the interface
A DMakefile9 psa-driver-interface.md \
/lib/lwip/lwip/contrib/ports/unix/
A DREADME11 * port/netif, port/include/netif: Various network interface implementations and
19 * pcapif: Network interface that replays packages from a PCAP dump file, and
24 * tapif: Network interface that is mapped to a tap interface (Unix user
/lib/mbedtls/external/mbedtls/docs/architecture/
A Dpsa-crypto-implementation-structure.md1 PSA Cryptography API implementation and PSA driver interface
6 …interface) defines an interface to cryptographic operations for which the Mbed TLS library provide…
8 … Mbed TLS PSA Cryptography API implementation which is tightly related to the PSA driver interface.
11 …interface. The key point is that software cryptographic operations are organized as PSA drivers: t…
15 * Addressing software and hardware cryptographic implementations through the same C interface reduc…
17 …nalities can be described by a JSON driver description file as defined in the PSA driver interface.
26 …ents and translating them into valid arguments for the necessary calls to the PSA driver interface.
35 /* Pre driver interface call processing: validation of arguments, building
36 * of arguments for the call to the driver interface, ... */
40 /* Call to the driver interface */
[all …]
/lib/lwip/lwip/contrib/apps/LwipMibCompiler/Mibs/IANA/
A DIANAifType-MIB339 isdns(75), -- ISDN S/T interface
340 isdnu(76), -- ISDN U interface
393 docsCableDownstream (128), -- CATV Downstream interface
394 docsCableUpstream (129), -- CATV Upstream interface
396 tunnel (131), -- Encapsulation interface
475 pon155 (207), -- FSAN 155Mb Symetrical PON interface
476 pon622 (208), -- FSAN622Mb Symetrical PON interface
477 bridge (209), -- Transparent bridge interface
482 mpegTransport (214), -- MPEG transport interface
483 sixToFour (215), -- 6to4 interface (DEPRECATED)
[all …]
/lib/lwip/lwip/doc/
A Dppp.txt1 PPP interface for lwIP
62 /* The PPP IP interface */
203 * Create a new PPPoS interface
205 * ppp_netif, netif to use for this PPP link, i.e. PPP IP interface
222 * Create a new PPPoE interface
224 * ppp_netif, netif to use for this PPP link, i.e. PPP IP interface
225 * ethif, already existing and setup Ethernet interface to use
245 * Create a new PPPoL2TP interface
247 * ppp_netif, netif to use for this PPP link, i.e. PPP IP interface
269 /* Set this interface as default route */
[all …]
A Dsavannah.txt35 documentation and a graphic user interface. Use its key generator.
121 You will have to submit this via the user News interface, then approve
122 this via the Administrator News interface.
A DFILES6 ppp.txt - Documentation of the PPP interface for lwIP.
/lib/mbedtls/external/mbedtls/
A DCONTRIBUTING.md35 …interface is required, all changes to the ABI or API, even on the main development branch where ne…
37 …interface which will change the API. Instead the interface can only be changed by its extension. W…
/lib/mbedtls/external/mbedtls/programs/
A DREADME.md8 …tion and authentication, demonstrating the generic cipher interface and the generic hash interface.
12 …neric_sum.c): file hash calculator and verifier, demonstrating the message digest (`md`) interface.
26 …y file and uses the key to encrypt/decrypt a short string through the generic public-key interface.
34 …blic/private key and uses it to encrypt/decrypt a short string through the low-level RSA interface.
50 * [`pkey/dh_genprime.c`](pkey/dh_genprime.c): shows how to use the bignum (`mpi`) interface to gene…
/lib/mbedtls/external/mbedtls/docs/architecture/psa-migration/
A Dmd-cipher-dispatch.md45 I want to have clear rules for when to use which interface,
196 * The requested mechanism is enabled in the legacy interface but not in the PSA interface. This was…
271 ### Designing an interface for hashes
279 A hash is available through the mixed-domain interface iff either of the following conditions is tr…
281 * A legacy hash interface is available and the hash algorithm is implemented in software.
284 …gacy hash interface, e.g. `md.h` or `shaX.h`. There is little point in doing this, however: caller…
300 #### Shape of the mixed-domain hash interface
310 The existing interface in `md.h` is close to what we want, but not perfect. What's wrong with it?
319 * We can make names and HMAC optional. The mixed-domain hash interface won't be the full `MBEDTLS_M…
390 …at implements the hash calculation interface described in ”[Designing an interface for hashes](#de…
[all …]
/lib/mbedtls/external/mbedtls/programs/psa/
A Dpsa_hash_demo.sh9 This program demonstrates the use of the PSA cryptography interface to

Completed in 65 milliseconds

123