| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | package_built_detail.html | 24 …strong>{{package.fullpackagespec}}</strong> is <strong>not included</strong> in any image. This pa…
39 <strong>{{package.fullpackagespec}}</strong> does not generate any files.
|
| H A D | package_built_dependencies.html | 23 <strong>{{package.fullpackagespec}}</strong> has no runtime dependencies.
27 …strong>{{package.fullpackagespec}}</strong> is <strong>not included</strong> in any image. This pa…
|
| H A D | customrecipe.html | 49 <p>Are you sure you want to delete the <strong>{{recipe.name}}</strong>
78 …mation from a previous build it is likely that adding <strong class="package-to-add-name"></strong…
84 …<p class="help-block text-left">Total package size: <strong id="package-deps-total-size"></strong>…
102 …strong class="reverse-deps-count"></strong> <span class="reverse-deps-package"></span> in your ima…
105 …ve <strong class="package-to-rm-name"></strong>, you must remove <span class="reverse-deps-this"><…
108 …class="help-block text-left">Total package size: <strong id="package-reverse-deps-total-size"></st…
119 …<p>Your custom image <strong>{{recipe.name}}</strong> has been created. You can now add or remove …
|
| H A D | layerdetails.html | 14 Are you sure you want to delete the <strong>{{layerversion.layer.name}}</strong> layer?
204 In a <strong>Git repository</strong>
211 In a <strong>directory</strong>
286 …<p>Toaster does not have recipe information for the <strong> {{layerversion.layer.name}} </strong>…
287 …ecipes, they will be listed here after you build the <strong> {{layerversion.layer.name}} </strong…
300 …<p>Toaster does not have machine information for the <strong> {{layerversion.layer.name}} </strong…
|
| H A D | basebuildpage.html | 67 …strong>{{build.get_sorted_target_list|field_values:"target"|join:", "}} {{build.machine}}</strong>…
74 …strong>{{build.get_sorted_target_list|field_values:"target"|join:", "}} {{build.machine}}</strong>…
|
| H A D | importlayer.html | 30 …The layer you are importing must be compatible with <strong>{{project.release.description}}</stron…
82 In a <strong>Git repository</strong>
89 In a <strong>directory</strong>
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/ |
| H A D | customrecipe.js | 151 msg += "<strong>" + (targetPkg.depsAdded.length + 1) + "</strong>";
153 msg += "<strong>" + targetPkg.name + "</strong> and its dependencies";
158 msg += " <strong>" + dep.name + "</strong>";
174 msg += "added <strong>1</strong>";
176 msg += "<strong>" + targetPkg.name + "</strong>";
221 msg += " <strong>" + targetPkg.name + "</strong>";
300 …var msg = $('<span>You have deleted <strong>1</strong> custom image: <strong id="deleted-custom-im…
|
| H A D | projectpage.js | 289 …sage = $('<span>You have changed the machine to: <strong><span id="notify-machine-name"></span></s…
343 …ssage = $('<span>You have changed the distro to: <strong><span id="notify-machine-name"></span></s…
376 …var msg = $('<span>You have deleted <strong>1</strong> project: <strong id="project-deleted"></st…
|
| H A D | importlayer.js | 141 var body = "<strong>"+layer.name+"</strong>'s dependencies ("+
207 …ve imported <strong><a class=\"alert-link\" href=\""+imported.imported_layer.layerdetailurl+"\">"+…
220 …strong><a href="'+imported.imported_layer.layerdetailurl+'">'+imported.imported_layer.name+'</a></…
|
| /openbmc/openbmc/poky/scripts/lib/build_perf/html/ |
| H A D | measurement_chart.html | 46 …return `<strong>Duration:</strong> ${hours}:${minutes}:${seconds}, <br/> <strong>Commit number:</s…
48 …return `<strong>Size:</strong> ${value.toFixed(2)} MB, <br/> <strong>Commit number:</strong> <a hr…
|
| /openbmc/linux/Documentation/w1/slaves/ |
| H A D | w1_therm.rst | 45 powered devices are detected on the bus (and strong pullup is enabled
57 A strong pullup will be applied during the conversion if required.
100 strong pullup, 1 to enable autodetection or 2 to force strong pullup.
103 If so, it will activate the master's strong pullup.
105 (seems to be the case with some DS18S20) the strong pullup can
108 If the strong pullup is enabled, the master's strong pullup will be
110 does support the strong pullup (or it falls back to a pullup
113 sufficient. The strong pullup is designed to provide the additional
|
| /openbmc/linux/drivers/hid/ |
| H A D | hid-emsff.c | 27 int weak, strong; in emsff_play() local
30 strong = effect->u.rumble.strong_magnitude; in emsff_play()
32 dbg_hid("called with 0x%04x 0x%04x\n", strong, weak); in emsff_play()
35 strong = strong * 0xff / 0xffff; in emsff_play()
38 emsff->report->field[0]->value[2] = strong; in emsff_play()
40 dbg_hid("running with 0x%02x 0x%02x\n", strong, weak); in emsff_play()
|
| H A D | hid-lg2ff.c | 27 int weak, strong; in play_effect() local
29 strong = effect->u.rumble.strong_magnitude; in play_effect()
32 if (weak || strong) { in play_effect()
34 strong = strong * 0xff / 0xffff; in play_effect()
38 lg2ff->report->field[0]->value[4] = strong; in play_effect()
|
| H A D | hid-mf.c | 38 int strong, weak; in mf_play() local
40 strong = effect->u.rumble.strong_magnitude; in mf_play()
43 dbg_hid("Called with 0x%04x 0x%04x.\n", strong, weak); in mf_play()
45 strong = strong * 0xff / 0xffff; in mf_play()
48 dbg_hid("Running with 0x%02x 0x%02x.\n", strong, weak); in mf_play()
51 mf->report->field[0]->value[1] = strong; in mf_play()
|
| H A D | hid-pl.c | 43 s32 *strong; member
61 *plff->strong = left; in hid_plff_play()
80 s32 *strong; in plff_init() local
120 strong = &report->field[0]->value[2]; in plff_init()
133 strong = &report->field[2]->value[0]; in plff_init()
158 plff->strong = strong; in plff_init()
162 *strong = 0x00; in plff_init()
|
| H A D | hid-dr.c | 36 int strong, weak; in drff_play() local
38 strong = effect->u.rumble.strong_magnitude; in drff_play()
41 dbg_hid("called with 0x%04x 0x%04x", strong, weak); in drff_play()
43 if (strong || weak) { in drff_play()
44 strong = strong * 0xff / 0xffff; in drff_play()
48 this value is set, it causes the strong rumble to function in drff_play()
56 drff->report->field[0]->value[4] = strong; in drff_play()
68 dbg_hid("running with 0x%02x 0x%02x", strong, weak); in drff_play()
|
| H A D | hid-holtekff.c | 43 * 1: very strong rumble
45 * 3: very strong rumble
50 * 8: strong periodic rumble, short intervals
51 * 9: very strong rumble
53 * b: very strong periodic rumble, very short intervals
56 * bit 7: left (strong) motor enabled
|
| /openbmc/linux/tools/memory-model/ |
| H A D | linux-kernel.cat | 55 let strong-fence = mb | gp
57 let nonrw-fence = strong-fence | po-rel | acq-po
87 (* Propagation: Ordering from release operations and strong fences. *)
90 let cumul-fence = [Marked] ; (A-cumul(strong-fence | po-rel) | wmb |
106 (* Propagation: Each non-rf link needs a strong fence. *)
107 let pb = prop ; strong-fence ; hb* ; [Marked]
130 * The synchronize_rcu() strong fence is special in that it can order not
139 * inter-CPU strong fence.
156 let strong-fence = strong-fence | rcu-fence
184 ((strong-fence ; [Marked] ; xbstar) | (xbstar & int))
[all …]
|
| /openbmc/linux/arch/xtensa/boot/lib/ |
| H A D | Makefile | 23 CFLAGS_REMOVE_inflate.o += -fstack-protector -fstack-protector-strong
24 CFLAGS_REMOVE_zmem.o += -fstack-protector -fstack-protector-strong
25 CFLAGS_REMOVE_inftrees.o += -fstack-protector -fstack-protector-strong
26 CFLAGS_REMOVE_inffast.o += -fstack-protector -fstack-protector-strong
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/snippets/ |
| H A D | pkg_dependencies_popover.html | 23 <strong>
30 </strong>
32 <strong>{{package_deps.size|filtered_filesizeformat}}</strong>'>
|
| H A D | pkg_revdependencies_popover.html | 23 <strong>
30 </strong>
32 <strong>{{package_deps.size|filtered_filesizeformat}}</strong>'>
|
| /openbmc/linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 512 Dependency types and strong dependency paths:
571 "strong" path, which indicates the strong dependency throughout each dependency
573 -(xR)-> and -(Sx)->. In other words, a "strong" path is a path from a lock
579 We will see why the path is called "strong" in next section.
588 If there is a closed strong path (i.e. a strong circle), then there is a
589 combination of locking sequences that causes deadlock. I.e. a strong circle is
594 If there is no closed strong path (i.e. strong circle), then there is no
595 combination of locking sequences that could cause deadlock. I.e. strong
598 With these two Lemmas, we can easily say a closed strong path is both sufficient
599 and necessary for deadlocks, therefore a closed strong path is equivalent to
[all …]
|
| /openbmc/linux/drivers/w1/ |
| H A D | w1_io.c | 97 * Pre-write operation, currently only supporting strong pullups.
98 * Program the hardware for a strong pullup, if one has been requested and
114 * Post-write operation, currently only supporting strong pullups.
115 * If a strong pullup was requested, clear it if the hardware supports
432 * w1_next_pullup() - register for a strong pullup
436 * Put out a strong pull-up of the specified duration after the next write
437 * operation. Not all hardware supports strong pullups. Hardware that
438 * doesn't support strong pullups will sleep for the given time after the
439 * write operation without a strong pullup. This is a one shot request for
|
| /openbmc/qemu/qobject/ |
| H A D | qstring.c | 20 * Return strong reference.
46 * Return strong reference.
56 * Return strong reference.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-extended/dlm/dlm/ |
| H A D | 0001-Remove-fcf-protection-full.patch | 24 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong \
35 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong \
46 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong \
|