/trusted-firmware-a-3.4.0/lib/zlib/ |
D | inftrees.c | 32 int ZLIB_INTERNAL inflate_table(type, lens, codes, table, bits, work) in inflate_table() argument 38 unsigned short FAR *work; 147 if (lens[sym] != 0) work[offs[lens[sym]]++] = (unsigned short)sym; 183 base = extra = work; /* dummy value--not used */ 217 if (work[sym] + 1U < match) { 219 here.val = work[sym]; 221 else if (work[sym] >= match) { 222 here.op = (unsigned char)(extra[work[sym] - match]); 223 here.val = base[work[sym] - match]; 254 len = lens[work[sym]];
|
D | inftrees.h | 62 unsigned FAR *bits, unsigned short FAR *work));
|
D | inflate.h | 120 unsigned short work[288]; /* work area for code table building */ member
|
D | inflate.c | 300 inflate_table(LENS, state->lens, 288, &(next), &(bits), state->work); 307 inflate_table(DISTS, state->lens, 32, &(next), &(bits), state->work); 950 &(state->lenbits), state->work); 1024 &(state->lenbits), state->work); 1033 &(state->next), &(state->distbits), state->work);
|
/trusted-firmware-a-3.4.0/ |
D | dco.txt | 21 (b) The contribution is based upon previous work that, to the best 24 work with modifications, whether created in whole or in part
|
/trusted-firmware-a-3.4.0/docs/components/spd/ |
D | tlk-dispatcher.rst | 5 to work with Trusted Firmware-A (TF-A). TLK-D can be compiled by including it 6 in the platform's makefile. TLK is primarily meant to work with Tegra SoCs,
|
/trusted-firmware-a-3.4.0/docs/plat/ |
D | rpi4.rst | 9 as a 64-bit Linux kernel. Other payloads such as U-Boot or EDK-II should work 31 arm64 Linux kernels are known to work this way. 82 would work as well, as long as it can cope with having the DT address in
|
D | qti-msm8916.rst | 13 trial and error to actually make it work. 39 management (``CPU_SUSPEND``) is functional but still work-in-progress and
|
D | socionext-uniphier.rst | 94 still work without SCP, but SCP provides better power management support.
|
D | rpi3.rst | 49 that we need to make the secondary cores work in the way the kernel expects, as 456 Just enter your credentials, everything should work as expected. Note that the
|
/trusted-firmware-a-3.4.0/fdts/ |
D | stm32mp157c-lxa-mc1.dts | 64 * work, thus enable internal pull-ups.
|
/trusted-firmware-a-3.4.0/docs/getting_started/ |
D | initial-build.rst | 37 work with TF-A). ``CROSS_COMPILE`` need not be set for Clang. Please note, 42 to work.
|
D | prerequisites.rst | 18 should also work fine as a base, provided that the necessary tools and libraries
|
/trusted-firmware-a-3.4.0/docs/plat/arm/fvp-ve/ |
D | index.rst | 8 This platform is tested on and only expected to work with single core models.
|
/trusted-firmware-a-3.4.0/docs/process/ |
D | code-review-guidelines.rst | 15 perspectives, depending on their past work, experiences and their current use 22 Code reviews are meant to benefit everyone through team work. It is not about 23 unfairly criticizing or belittling the work of any contributor.
|
D | coding-guidelines.rst | 360 definitions, consider how padding in the struct will work across architectures. 396 may work but is less portable.
|
/trusted-firmware-a-3.4.0/docs/plat/marvell/armada/ |
D | porting.rst | 30 In most cases, using the default address decode windows should work OK. 37 For a detailed information on how CCU, IOWIN, AXI-MBUS & IOB work, please
|
/trusted-firmware-a-3.4.0/docs/design/ |
D | alt-boot-flows.rst | 60 It is expected that this loading method will work in most cases, as a debugger
|
/trusted-firmware-a-3.4.0/docs/security_advisories/ |
D | security-advisory-tfv-3.rst | 34 This feature does not work correctly for AArch64 images executing at Secure EL1.
|
D | security-advisory-tfv-4.rst | 46 This macro does not work correctly for AArch32 images. It fails to detect
|
D | security-advisory-tfv-6.rst | 61 work. If that other privileged software is able to workaround the vulnerability
|
/trusted-firmware-a-3.4.0/docs/components/ |
D | debugfs-design.rst | 104 the internal work buffer, and re-entrancy into the filesystem layers.
|
D | romlib-design.rst | 78 files for the "library at ROM" to work. It implements multiple functions:
|
D | ras.rst | 147 work, the platform must setup and register with |EHF|. See `Interaction with
|
/trusted-firmware-a-3.4.0/docs/plat/nxp/ |
D | nxp-ls-tbbr.rst | 58 …-- For this to work, file name for cert and keys are provided as part of compilation or build com…
|