| /openbmc/linux/arch/m68k/ |
| H A D | Kconfig.machine | 40 computers. If you plan to use this kernel on a Mac, say Y here and
58 Say Y here if you want to build a kernel for a 680x0 based VME
70 build a kernel which can run on MVME147 single-board computers. If
80 Say Y to include support for Motorola VME boards. This will build a
93 build a kernel which can run on BVME4000 and BVME6000 boards. If
105 experimental. If you plan to try to use the kernel on such a machine
122 If you don't want to compile a kernel for a Sun 3x, say N.
130 The Q40 is a Motorola 68040-based successor to the Sinclair QL
150 If you don't want to compile a kernel exclusively for a Sun 3, say N.
167 This options enable a pure virtual machine based on m68k,
[all …]
|
| /openbmc/linux/arch/sparc/kernel/ |
| H A D | mdesc.c | 322 u64 a; in parent_cfg_handle() local
325 mdesc_for_each_arc(a, hp, node, MDESC_ARC_TYPE_BACK) { in parent_cfg_handle()
328 target = mdesc_arc_target(hp, a); in parent_cfg_handle()
422 struct mdesc_handle *a, in invoke_on_missing() argument
450 mdesc_for_each_node_by_name(a, a_node, name) { in invoke_on_missing()
453 rv = get_info_func(a, a_node, &a_node_info); in invoke_on_missing()
478 func(a, a_node, name); in invoke_on_missing()
849 u64 a; in fill_in_one_cache() local
851 mdesc_for_each_arc(a, hp, mp, MDESC_ARC_TYPE_FWD) { in fill_in_one_cache()
852 u64 target = mdesc_arc_target(hp, a); in fill_in_one_cache()
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | interface-overview.md | 3 Purpose: This introduces a simplified view of the BMC's primary interfaces. It
4 is intended to provide a reference suitable for a wide audience:
8 - Give BMC administrators and system integrators a simplified view of the BMC's
19 project in a framework to reason about which interfaces are present, how they
20 are related. This provides a foundation to reason about which can be disabled,
28 details from the unit file may be shown, such as the program which implements a
32 example, disabling a BMC service will disable the corresponding external
47 and connections to its host platform. This uses a simplified view of the host
167 the BMC as a Unix domain socket.
173 OpenBMC provides a custom HTTP/Web server called BMCWeb.
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | SGI-B-1.0 | 14 …1.5 "Larger Work" means a work which combines Covered Code or portions thereof with code not gover…
20 …ion from previous Modifications. When Covered Code is released as a series of files, a Modificatio…
22 …A. Any addition to the contents of a file containing Original Code and/or any addition to or delet…
30 …a legal entity exercising rights under, and complying with all of the terms of, this License or a …
36 …a worldwide, royalty-free, non-exclusive license, to do the following: (i) under copyrights Licens…
46 …ice must appear in every file that can include a text comments field; in executable form, the Noti…
48 …a license identical to this License but for only such changes as are necessary in order to clarify…
50 …C. Indemnity. Recipient hereby agrees to indemnify SGI for any liability incurred by SGI as a resu…
60 … License from time to time, each with a distinguishing version number. Once Covered Code has been …
68 12. U.S. Government End Users. The Covered Code is a "commercial item" consisting of "commercial co…
[all …]
|
| H A D | OGL-UK-1.0 | 3 …e under this licence, the Open Government Licence, freely and flexibly, with only a few conditions.
8 The Licensor grants you a worldwide, royalty-free, perpetual, non-exclusive licence to use the Info…
18 …ement specified by the Information Provider(s) and, where possible, provide a link to this licence;
19 … If the Information Provider does not provide a specific attribution statement, or if you are usin…
20 …ensure that you do not use the Information in a way that suggests any official status or that the …
31 … logos, crests and the Royal Arms except where they form an integral part of a document or dataset;
57 …a verb, means doing any act which is restricted by copyright or database right, whether in the ori…
62 … this licence as a tool to enable Information Providers in the public sector to license the use an…
|
| H A D | OGL-UK-2.0 | 3 …e Information that is available under this licence freely and flexibly, with only a few conditions.
8 The Licensor grants you a worldwide, royalty-free, perpetual, non-exclusive licence to use the Info…
17 …ement specified by the Information Provider(s) and, where possible, provide a link to this licence;
18 …If the Information Provider does not provide a specific attribution statement, or if you are using…
29 … logos, crests and the Royal Arms except where they form an integral part of a document or dataset;
35 This licence does not grant you any right to use the Information in a way that suggests any officia…
58 …, copying, adapting, modifying as may be technically necessary to use it in a different mode or fo…
64 … this licence as a tool to enable Information Providers in the public sector to license the use an…
68 … of the Open Government Licence. If you are already using Information under a previous version of …
|
| H A D | FTL | 13 …sion and use of free software in commercial and freeware products alike. As a consequence, its mai…
19 …o You may not pretend that you wrote this software. If you use it, or only parts of it, in a progr…
23 Finally, many people asked us for a preferred form for a credit/disclaimer to use in compliance wit…
35 …a generic term including compiling the project's source code as well as linking it to form a `prog…
37 …rm as distributed in the original archive. If you are unsure whether or not a particular file is c…
47 This license grants a worldwide, royalty-free, perpetual and irrevocable right and license to use, …
51 …o Redistribution in binary form must provide a disclaimer that states that the software is based i…
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | design.rst | 25 For data access monitoring and additional low level work, DAMON needs a set of
47 Core layer of DAMON is implemented as a framework, and exposes its application
77 mapping is not strictly required but could even incur a high overhead in some
88 to make a reasonable trade-off. Below shows this in detail::
107 table having a mapping to the address. In this way, the implementations find
133 The output of DAMON says what pages are how frequently accessed for a given
161 that assumed to have the same access frequencies into a region. As long as the
162 assumption (pages in a region have the same access frequencies) is kept, only
197 access pattern of a region has maintained. That could be used for good
217 abstracted monitoring target memory area only for each of a user-specified time
[all …]
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | inodes.rst | 6 In a regular UNIX filesystem, the inode stores all the metadata
8 etc), not the directory entry. To find the information associated with a
10 associated with a file, then load the inode to find the metadata for
11 that file. ext4 appears to cheat (for performance reasons) a little bit
12 by storing a copy of the file type (normally stored in the inode) in the
18 The inode table is a linear array of ``struct ext4_inode``. The table is
85 which means that there cannot be more than 64,998 subdirectories in a
86 directory (each subdirectory's '..' entry counts as a hard link, as does
121 many possible extended attributes; I think the name of this field is a
177 The ``i_mode`` value is a combination of the following flags:
[all …]
|
| /openbmc/linux/drivers/media/platform/rockchip/rkisp1/ |
| H A D | rkisp1-regs.h | 327 #define RKISP1_CIF_MIPI_CTRL_SHUTDOWNLANES(a) (((a) & 0xF) << 8) argument
328 #define RKISP1_CIF_MIPI_CTRL_NUM_LANES(a) (((a) & 0x3) << 12) argument
334 #define RKISP1_CIF_MIPI_DATA_SEL_VC(a) (((a) & 0x3) << 6) argument
335 #define RKISP1_CIF_MIPI_DATA_SEL_DT(a) (((a) & 0x3F) << 0) argument
338 #define RKISP1_CIF_MIPI_SYNC_FIFO_OVFLW(a) (((a) & 0xF) << 0) argument
339 #define RKISP1_CIF_MIPI_ERR_SOT(a) (((a) & 0xF) << 4) argument
340 #define RKISP1_CIF_MIPI_ERR_SOT_SYNC(a) (((a) & 0xF) << 8) argument
341 #define RKISP1_CIF_MIPI_ERR_EOT_SYNC(a) (((a) & 0xF) << 12) argument
342 #define RKISP1_CIF_MIPI_ERR_CTRL(a) (((a) & 0xF) << 16) argument
440 #define RKISP1_CIFFLASH_CONFIG_DELAY(a) (((a) & 0xF) << 4) argument
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | kernel-fitimage.bbclass | 141 …if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a -n "$kernel_sign_keyname" ]…
188 …if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a -n "$dtb_sign_keyname" ] ; …
225 …if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a -n "$bootscr_sign_keyname" …
301 …if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a -n "$ramdisk_sign_keyname" …
316 # $1 ... file that's a potential symlink
521 …if [ -n "${UBOOT_SIGN_IMG_KEYNAME}" -a "${UBOOT_SIGN_KEYNAME}" = "${UBOOT_SIGN_IMG_KEYNAME}" ]; th…
528 # Step 1: Prepare a kernel image section.
536 # Step 2: Prepare a DTB image section
594 # Also skip if a symlink. We'll later have each config section point at it
607 # Step 3: Prepare a u-boot script section
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | user-guide.rst | 13 a tiny Linux distribution suitable for the Corstone-1000 platform (kernel and initramfs filesystem …
58 a `BitBake recipe <https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manua…
81 `Trusted Firmware-A <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`__
85 | bbappend | ``$WORKSPACE/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%…
87 | Recipe | ``$WORKSPACE/meta-arm/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a_2.11.…
146 distribution which is a Linux distribution stripped down to a minimal configuration.
199 #. Create a new folder that will be your workspace.
221 #. Build a Corstone-1000 image:
230 to build a Corstone-1000 image for FVP as follows:
246 A clean build takes a significant amount of time given that all of the development machine utilitie…
[all …]
|
| /openbmc/qemu/hw/display/ |
| H A D | exynos4210_fimd.c | 262 uint32_t a; member
389 p->a = (pixel & 0x1); \
411 p->a = 0x0; \
432 p->a = (pixel & ((1 << (A)) - 1)) << (8 - (A)) | \
434 p->a = p->a | (p->a << 8) | (p->a << 16); \
457 p->a = (pixel & 0x1); in pixel_a232_to_rgb()
470 p->a = 0x0; in pixel_1555_to_rgb()
480 *(uint32_t *)d = p.a; in put_pixel_ifb()
489 p->a = (*(uint32_t *)s) & 0x00FFFFFF; in get_pixel_ifb()
552 static inline uint32_t fimd_mult_each_byte(uint32_t a, uint32_t b) in fimd_mult_each_byte() argument
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/ipw2x00/ |
| H A D | Kconfig | 23 In order to use this driver, you will need a firmware image for it.
33 It is recommended that you compile this driver as a module (M)
39 including the firmware and a firmware loader in an initramfs.
85 In order to use this driver, you will need a firmware image for it.
95 It is recommended that you compile this driver as a module (M)
101 including the firmware and a firmware loader in an initramfs.
117 bool "Enable creation of a RF radiotap promiscuous interface"
121 Enables the creation of a second interface prefixed 'rtap'.
134 If you do not specify 'rtap_iface=1' as a module parameter then
191 For a list of values you can assign to debug_level, you
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/openssl/openssl/ |
| H A D | 0001-Added-handshake-history-reporting-when-test-fails.patch | 15 diff --git a/test/helpers/handshake.c b/test/helpers/handshake.c
17 --- a/test/helpers/handshake.c
98 + * Create a new history entry for a handshake loop with statuses given in
198 diff --git a/test/helpers/handshake.h b/test/helpers/handshake.h
200 --- a/test/helpers/handshake.h
208 * this file except in compliance with the License. You can obtain a copy
257 +/* Stores the various status information in a handshake loop. */
303 diff --git a/test/ssl_test.c b/test/ssl_test.c
305 --- a/test/ssl_test.c
|
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A D | sonypi.rst | 14 limited to new FX series laptops, at least the FX501 and the FX702) lack a
17 It will give access (through a user space utility) to some events those laptops
28 /dev/sonypi (major 10, minor auto allocated or specified as a option).
45 specs for its laptops. If someone convinces them to do so, drop me a note.
60 camera: if you have a PictureBook series Vaio (with the
87 not have a jogdial but reuses the jogdial events for
111 mouse events, the other one which acts like a
119 lines a configuration file in /etc/modprobe.d/::
150 - some models with the nvidia card (geforce go 6200 tc) uses a
152 is a userspace utility to adjust the brightness on those models,
|
| /openbmc/linux/Documentation/fb/ |
| H A D | vesafb.rst | 5 This is a generic driver for a graphic framebuffer on intel boxes.
14 Version 2.0 are required, because we need a linear frame buffer.
18 * It provides a nice large console (128 cols + 48 lines with 1024x768)
77 Extensions v2.0 are required, 1.2 is NOT sufficient. You will get a
93 with a broken console (and vesafb cannot do anything about this).
105 * use a native driver (matroxfb/atyfb) instead if vesafb. If none
106 is available, write a new one!
107 * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0
130 interface. The visible screen is just a window of the
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-ipmi | 83 (RO) Displays a number that identifies a particular system,
96 (RO) A GUID (Globally Unique ID), also referred to as a UUID
144 requested a timer while nothing was in
157 requested a timer while an operation was
168 disables interrupts when it gets into a situation where it
228 flag_fetches (RO) Number of times a flag fetch was
231 send_retries (RO) Number of time a message was
234 receive_retries (RO) Number of times the receive of a
237 send_errors (RO) Number of times the send of a
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | cx2341x-uapi.rst | 10 format of a YUV frame is 16x16 linear tiled NV12 (V4L2_PIX_FMT_NV12_16L16).
38 The width of a frame is always 720 pixels, regardless of the actual specified
41 If the height is not a multiple of 32 lines, then the captured video is
42 missing macroblocks at the end and is unusable. So the height must be a
139 chips), in particular a maximum size for the VBI data. Anything longer is cut
146 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
147 header and a 42 bytes payload each. Anything beyond this limit is cut off by
149 for a bitmask determining which lines are captured and 4 bytes for a magic cookie,
|
| /openbmc/linux/arch/m68k/ifpsp060/ |
| H A D | os.S | 23 |You are hereby granted a copyright license to use, modify, and distribute the SOFTWARE
61 | When installing the 060SP, the _copyin()/_copyout() equivalents for a
65 | The result is that Unix processes are allowed to sleep as a consequence
66 | of a page fault during a _copyout.
140 | Read a data byte from user memory.
163 | Read a data word from user memory.
234 | Write a data byte to user memory.
256 | Write a data word to user memory.
280 | Write a data longword to user memory.
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | volatile-considered-harmful.rst | 13 a volte saranno tentati dall'utilizzare *volatile* nel kernel per le
32 In un pezzo di codice kernel scritto a dovere, *volatile* può solo servire a
56 trattiene un lock, il dato condiviso non è *volatile*. Quando si ha a che
89 sezione critica a se stante, e garantisce che l'accesso avvenga secondo
94 la parola chiave *volatile* a questo codice ne previene la rimozione.
103 - I puntatori a delle strutture dati in una memoria coerente che potrebbe
104 essere modificata da dispositivi di I/O può, a volte, essere legittimamente
111 visto come un baco e porterà a verifiche aggiuntive. Gli sviluppatori tentati
112 dall'uso di *volatile* dovrebbero fermarsi e pensare a cosa vogliono davvero
|
| H A D | deprecated.rst | 22 cosa è considerato deprecato (e perché), è stata create la seguente lista a cui
34 deve essere rimossa dal kernel, o aggiunta a questo documento per scoraggiarne
56 volete avvisare gli utenti riguardo a qualcosa di possibile anche se
68 (o simili) per via del rischio di overflow. Questo può portare a valori più
79 Al suo posto, si dovrebbe usare l'allocatore a due argomenti::
103 invitati a riorganizzare il vostro codice usando il
117 Per maggiori dettagli fate riferimento a array3_size() e flex_array_size(), ma
125 i possibili overflow, e questo può portare il chiamante a generare risultati
137 a ridurne il rischio, non c'è alcuna buona ragione per continuare ad usare
139 prestata attenzione a tutti quei casi dove viene usato il valore di
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/ |
| H A D | nodejs_22.13.1.bb | 49 def map_nodejs_arch(a, d):
52 if re.match('i.86$', a): return 'ia32'
53 elif re.match('x86_64$', a): return 'x64'
54 elif re.match('aarch64$', a): return 'arm64'
55 elif re.match('(powerpc64|powerpc64le|ppc64le)$', a): return 'ppc64'
56 elif re.match('powerpc$', a): return 'ppc'
57 return a
99 # binaries must have the same bit-width as the target (e.g. a x86_64
100 # host targeting ARMv6 needs to produce a 32-bit binary).
106 """Creates a small wrapper that invokes QEMU to run some target V8 binaries
|
| /openbmc/qemu/target/ppc/ |
| H A D | fpu_helper.c | 39 static inline float32 bfp32_neg(float32 a) in bfp32_neg() argument
41 if (unlikely(float32_is_any_nan(a))) { in bfp32_neg()
42 return a; in bfp32_neg()
44 return float32_chs(a); in bfp32_neg()
648 static float64 do_fmadd(CPUPPCState *env, float64 a, float64 b, in do_fmadd() argument
651 float64 ret = float64_muladd(a, b, c, madd_flags, &env->fp_status); in do_fmadd()
660 static uint64_t do_fmadds(CPUPPCState *env, float64 a, float64 b, in do_fmadds() argument
663 float64 ret = float64r32_muladd(a, b, c, madd_flags, &env->fp_status); in do_fmadds()
795 uint64_t helper_FSEL(uint64_t a, uint64_t b, uint64_t c)
799 fa.ll = a;
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-graphics/mesa/mesa-demos/ |
| H A D | 0001-mesa-demos-Add-missing-data-files.patch | 43 diff --git a/src/fpglsl/depth-read.glsl b/src/fpglsl/depth-read.glsl
53 diff --git a/src/fpglsl/infinite-loop.glsl b/src/fpglsl/infinite-loop.glsl
66 diff --git a/src/glsl/CH11-bumpmaptex.frag b/src/glsl/CH11-bumpmaptex.frag
119 diff --git a/src/glsl/blinking-teapot.frag b/src/glsl/blinking-teapot.frag
156 diff --git a/src/glsl/blinking-teapot.vert b/src/glsl/blinking-teapot.vert
178 diff --git a/src/glsl/convolution.frag b/src/glsl/convolution.frag
205 diff --git a/src/glsl/simplex-noise.glsl b/src/glsl/simplex-noise.glsl
274 +// ( N points uniformly over a line, mapped onto a diamond.)
294 +// N points around a unit circle.
356 +// ( N*N points uniformly over a square, mapped onto a octohedron.)
[all …]
|