| /openbmc/qemu/ui/ |
| H A D | shader.c | 109 GLuint program; in qemu_gl_create_link_program() local
113 program = glCreateProgram(); in qemu_gl_create_link_program()
114 glAttachShader(program, vert); in qemu_gl_create_link_program()
115 glAttachShader(program, frag); in qemu_gl_create_link_program()
116 glLinkProgram(program); in qemu_gl_create_link_program()
118 glGetProgramiv(program, GL_LINK_STATUS, &status); in qemu_gl_create_link_program()
120 glGetProgramiv(program, GL_INFO_LOG_LENGTH, &length); in qemu_gl_create_link_program()
122 glGetProgramInfoLog(program, length, &length, errmsg); in qemu_gl_create_link_program()
127 return program; in qemu_gl_create_link_program()
133 GLuint vert_shader, frag_shader, program = 0; in qemu_gl_create_compile_link_program() local
[all …]
|
| /openbmc/linux/drivers/pwm/ |
| H A D | pwm-stmpe.c | 103 u16 program[3] = { in stmpe_24xx_pwm_config() local
158 program[0] = SMAX; /* off all the time */ in stmpe_24xx_pwm_config()
161 program[0] = LOAD | 0xff; /* LOAD 0xff */ in stmpe_24xx_pwm_config()
166 program[0] = SMIN; /* on all the time */ in stmpe_24xx_pwm_config()
169 program[0] = LOAD | 0x00; /* LOAD 0x00 */ in stmpe_24xx_pwm_config()
199 program[0] = LOAD | value; in stmpe_24xx_pwm_config()
200 program[1] = 0x0000; in stmpe_24xx_pwm_config()
213 program[0] = PRESCALE_512 | STEPTIME_1 | incdec; in stmpe_24xx_pwm_config()
216 program[1] = BRANCH; in stmpe_24xx_pwm_config()
221 pwm->hwpwm, value, last, program[0], program[1], in stmpe_24xx_pwm_config()
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | s390-dasd-ipl.rst | 19 location ``0x0``. Then the ccw program at ``0x08`` which consists of a read
23 program contained in the IPL2 data. The TIC channel command is the
29 The TIC ccw instruction at the end of the IPL1 channel program will begin
30 the execution of the IPL2 channel program. IPL2 is stage-2 of the boot
31 process and will contain a larger channel program than IPL1. The point of
32 IPL2 is to find and load either the operating system or a small program that
39 NOTE: The IPL2 channel program might read data into memory
40 location ``0x0`` thereby overwriting the IPL1 psw and channel program. This is ok
58 off the reading of IPL1 data. Since the channel program from IPL1 will be
59 written immediately after the special "Read IPL" ccw, the IPL1 channel program
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MakeIndex | 15 …program provided that the copyright notice and this permission notice are preserved and provided t…
17 …program under the conditions above with the additional requirement that the entire modified work m…
19 This program is distributed with no warranty of any sort. No contributor accepts responsibility fo…
|
| H A D | NAIST-2003 | 33 The program was produced on an experimental basis in the course of the
36 program is provided without any warranty whatsoever, whether express,
40 the program and the nonexistence of any infringement or violation of
43 Each user of the program will agree and understand, and be deemed to
45 the program and, accordingly, the entire risk arising from or
46 otherwise connected with the program is assumed by the user.
50 development of the program and their respective officials, directors,
54 with the use or inability to use the program or any product, material
55 or result produced or otherwise obtained by using the program,
59 foregoing by his or her commencement of use of the program. The term
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/util-linux/util-linux/ |
| H A D | fcntl-lock.c | 64 const char *program; variable
82 program); in usage()
145 program = argv[0]; in main()
195 program, argv[optind+1]); in main()
222 program, argv[optind], strerror(err)); in main()
233 fprintf(stderr, _("%s: bad number: %s\n"), program, argv[optind]); in main()
241 program); in main()
278 fprintf(stderr, "%s: %s: %s\n", program, filename, strerror(err)); in main()
280 fprintf(stderr, "%s: %d: %s\n", program, fd, strerror(err)); in main()
301 fprintf(stderr, _("%s: fork failed: %s\n"), program, strerror(err)); in main()
[all …]
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | run_keyword.robot | 5 # keyword_string The keyword string to be run by this program. If this
13 # test_mode This means that this program should go through all the
15 # debug If this parameter is set to "1", this program will print
17 # quiet If this parameter is set to "1", this program will print
38 # Initialize program parameters variables.
39 # Create parm_list containing all of our program parameters. parm_list is
44 # Initialize each program parameter.
54 [Documentation] Run the keyword program.
59 [Documentation] Do main program processing.
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | prog_sk_lookup.rst | 4 BPF sk_lookup program
7 BPF sk_lookup program type (``BPF_PROG_TYPE_SK_LOOKUP``) introduces programmability
11 When invoked BPF sk_lookup program can select a socket that will receive the
19 BPF sk_lookup program type was introduced to address setup scenarios where
36 BPF sk_lookup program can be attached to a network namespace with
53 verdict code. As for other BPF program types that are network filters,
58 A BPF sk_lookup program can also select a socket to receive the packet by
59 calling ``bpf_sk_assign()`` BPF helper. Typically, the program looks up a socket
62 selection. Selecting a socket only takes effect if the program has terminated
68 1. If any program returned ``SK_PASS`` and selected a valid socket, the socket
[all …]
|
| H A D | bpf_prog_run.rst | 19 execute a BPF program in the kernel and return the results to userspace. This
44 object and (for program types operating on network packets) a buffer containing
45 the packet data that the BPF program will operate on. The kernel will then
46 execute the program and return the results to userspace. Note that programs will
48 will not actually be redirected or dropped, the program return code will just be
57 be processed by the kernel after the execution of the XDP program as if they
59 ``BPF_F_TEST_XDP_LIVE_FRAMES`` flag when supplying an XDP program to
63 XDP program many times (suitable for, e.g., running as a traffic generator),
67 - When executing an XDP program in live frame mode, the result of the execution
69 operation indicated by the program's return code (drop the packet, redirect
[all …]
|
| H A D | bpf_iterators.rst | 34 A BPF iterator is a type of BPF program that allows users to iterate over
45 A BPF program is always loaded into the kernel at the behest of a user space
46 process. A user space process loads a BPF program by opening and initializing
47 the program skeleton as required and then invoking a syscall to have the BPF
48 program verified and loaded by the kernel.
50 In traditional tracing programs, a program is activated by having user space
51 obtain a ``bpf_link`` to the program with ``bpf_program__attach()``. Once
52 activated, the program callback will be invoked whenever the tracepoint is
54 program is obtained using ``bpf_link_create()``, and the program callback is
66 a BPF iterator program. To begin, we’ll look at `bpf_iter.c
[all …]
|
| H A D | map_cgroup_storage.rst | 11 storage is identified by the cgroup the program is attached to.
13 The map provide a local storage at the cgroup that the BPF program is attached
34 ``attach_type`` is the program's attach type.
42 To access the storage in a program, use ``bpf_get_local_storage``::
67 int program(struct __sk_buff *skb)
102 int program(struct __sk_buff *skb)
131 for a single ``CGROUP_STORAGE`` map, there can be at most one program loaded
132 that uses the map. A program may be attached to multiple cgroups or have
137 non-per-CPU) and the BPF program during load verification time. As a result,
138 each map can only be used by one BPF program and each BPF program can only use
[all …]
|
| H A D | prog_cgroup_sockopt.rst | 7 ``BPF_PROG_TYPE_CGROUP_SOCKOPT`` program type can be attached to two
26 If BPF program sets ``optlen`` to -1, the control will be returned
38 * ``1`` - success, continue with next BPF program in the cgroup chain.
62 the BPF program from the parent cgroup).
76 the programs are executed from the bottom up: B, A. First program
79 control will be passed to the second (A) program which will see the
82 Same for ``BPF_CGROUP_SETSOCKOPT``: if the program is attached to
85 then the next program in the chain (A) will see those changes,
91 When the ``optval`` is greater than the ``PAGE_SIZE``, the BPF program
96 done by the BPF program to the ``optval`` are ignored.
[all …]
|
| H A D | prog_cgroup_sysctl.rst | 7 This document describes ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program type that
17 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program to a cgroup.
23 BPF program::
49 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program must return one of the following
55 If program returns ``0`` user space will get ``-1`` from ``read(2)`` or
65 ``/proc/sys`` into provided by BPF program buffer;
68 sysctl into provided by BPF program buffer. This helper is available on both
78 has to be overridden BPF program can set ``file_pos`` to zero before calling
83 BPF program sees sysctl value same way as user space does in proc filesystem,
98 See `test_sysctl_prog.c`_ for an example of BPF program in C that access
[all …]
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hid-bpf.rst | 38 HID-BPF allows the userspace program to load the program itself, ensuring we
48 We can reduce this burden by providing an eBPF program instead. Once such a
49 program has been verified by the user, we can embed the source code into the
50 kernel tree and ship the eBPF program and load it directly instead of loading
80 events into wheel events. Also, the userspace program can set/unset the haptic
96 kernel/bpf program because we can intercept any incoming command.
119 program.
128 When a BPF program needs to emit input events, it needs to talk with the HID
144 A ``hid_bpf_device_event`` is calling a BPF program when an event is received from
153 BPF program of this type. This is called on ``probe`` from the driver and allows to
[all …]
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | ELF.rst | 10 "First" program header is the one with the smallest offset in the file:
13 "Last" program header is the one with the biggest offset in the file:
19 First PT_INTERP program header is used to locate the filename of ELF
25 Last PT_GNU_STACK program header defines userspace stack executability
31 ELF interpreter's last PT_GNU_PROPERTY program header is used (since
33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /openbmc/linux/drivers/fpga/ |
| H A D | lattice-sysconfig.c | 91 struct gpio_desc *program = priv->program; in sysconfig_gpio_refresh() local
97 gpiod_set_value(program, 1); in sysconfig_gpio_refresh()
107 gpiod_set_value(program, 0); in sysconfig_gpio_refresh()
128 struct gpio_desc *program = priv->program; in sysconfig_refresh() local
132 if (program && init && done) in sysconfig_refresh()
355 struct gpio_desc *program, *init, *done; in sysconfig_probe() local
370 program = devm_gpiod_get_optional(dev, "program", GPIOD_OUT_LOW); in sysconfig_probe()
371 if (IS_ERR(program)) in sysconfig_probe()
372 return dev_err_probe(dev, PTR_ERR(program), in sysconfig_probe()
385 priv->program = program; in sysconfig_probe()
|
| /openbmc/linux/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-cgroup.rst | 52 Output will start with program ID followed by attach type,
53 attach flags and program name.
66 program ID, attach type, attach flags and program name.
73 Attach program *PROG* to the cgroup *CGROUP* with attach type
77 some bpf program, the program in this cgroup yields to sub-cgroup
78 program; **multi** if a sub-cgroup installs some bpf program,
79 that cgroup program gets run in addition to the program in this
82 Only one program is allowed to be attached to a cgroup with
84 program will release old program and attach the new one.
|
| H A D | bpftool-prog.rst | 75 Output will start with program ID followed by program type and
79 programs (such as the total time spent running the program,
83 program run. Activation or deactivation of the feature is
99 **visual** is specified, *PROG* must match a single program.
113 Dump jited image (host machine code) of the program.
117 *PROG* must match a single program when **file** is specified.
126 Pin program *PROG* as *FILE*.
133 Load bpf program(s) from binary *OBJ* and pin as *PATH*.
134 **bpftool prog load** pins only the first program from the
137 **type** is optional, if not specified program type will be
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/syslinux/syslinux/ |
| H A D | 0002-linux-syslinux-implement-open_ext2_fs.patch | 44 extern const char *program; /* Name of program */
55 fprintf(stderr, "%s: %s\n", program, msg);
77 + program, device);
86 + program, device);
91 + fprintf(stderr, "%s: %s is mounted\n", program, device);
101 + program, device);
109 + program, device);
119 + program, subdir, device);
125 + fprintf(stderr, "%s: failed to cd to: %s\n", program, subdir);
|
| /openbmc/openbmc-test-automation/templates/ |
| H A D | pgm_template.robot | 3 # Copy this template as a base to get a start on a robot program. You may remove any generic commen…
6 Documentation Base to get a start on a robot program.
19 # Initialize program parameters variables.
20 # Create parm_list containing all of our program parameters.
23 # Initialize each program parameter.
|
| /openbmc/openbmc/meta-nuvoton/recipes-nuvoton/program-edid/ |
| H A D | program-edid.bb | 2 DESCRIPTION = "Add program EDID data support for DDC to SMB internal \
12 SRC_URI = "file://program-edid.service \
13 file://program-edid.sh \
18 SYSTEMD_SERVICE:${PN} = "program-edid.service"
28 install -m 0755 ${UNPACKDIR}/program-edid.sh ${D}${bindir}/
|
| /openbmc/linux/security/tomoyo/ |
| H A D | domain.c | 231 && p1->program == p2->program; in tomoyo_same_transition_control()
247 char *program = param->data; in tomoyo_write_transition_control() local
248 char *domainname = strstr(program, " from "); in tomoyo_write_transition_control()
255 domainname = program; in tomoyo_write_transition_control()
256 program = NULL; in tomoyo_write_transition_control()
258 if (program && strcmp(program, "any")) { in tomoyo_write_transition_control()
259 if (!tomoyo_correct_path(program)) in tomoyo_write_transition_control()
261 e.program = tomoyo_get_name(program); in tomoyo_write_transition_control()
262 if (!e.program) in tomoyo_write_transition_control()
280 tomoyo_put_name(e.program); in tomoyo_write_transition_control()
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/konkretcmpi/konkretcmpi/ |
| H A D | 0001-drop-including-rpath-cmake-module.patch | 14 src/program/CMakeLists.txt | 1 -
29 diff --git a/src/program/CMakeLists.txt b/src/program/CMakeLists.txt
31 --- a/src/program/CMakeLists.txt
32 +++ b/src/program/CMakeLists.txt
|
| /openbmc/linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 5 This document describes how an eXpress Data Path (XDP) program can access
23 An XDP program can use these kfuncs to read the metadata into stack
25 consumers, an XDP program can store it into the metadata area carried
44 An XDP program can store individual metadata items into this ``data_meta``
53 program that redirects XDP frames into the ``AF_XDP`` socket (``XSK``) and
54 the final consumer. Thus the BPF program manually allocates a fixed number of
74 This is the path where the packets processed by the XDP program are passed
82 In the future, we'd like to support a case where an XDP program
90 program after the redirect. However, the final consumer doesn't have
96 currently supported, which has to be prepared by the initial XDP program
[all …]
|
| /openbmc/linux/include/trace/events/ |
| H A D | sunrpc.h | 181 __string(program, clnt->cl_program->name)
191 __assign_str(program, clnt->cl_program->name);
200 __get_str(program), __get_str(server),
208 const char *program,
213 TP_ARGS(program, server, error),
217 __string(program, program)
223 __assign_str(program, program);
228 __get_str(program), __get_str(server), __entry->error)
1387 __field(unsigned int, program)
1397 __entry->program = clnt->cl_prog;
[all …]
|