/openbmc/linux/scripts/ |
H A D | markup_oops.pl | 49 if ($line =~ /EAX: ([0-9a-f]+) EBX: ([0-9a-f]+) ECX: ([0-9a-f]+) EDX: ([0-9a-f]+)/) { 55 if ($line =~ /ESI: ([0-9a-f]+) EDI: ([0-9a-f]+) EBP: ([0-9a-f]+) ESP: ([0-9a-f]+)/) { 60 if ($line =~ /RAX: ([0-9a-f]+) RBX: ([0-9a-f]+) RCX: ([0-9a-f]+)/) { 65 if ($line =~ /RDX: ([0-9a-f]+) RSI: ([0-9a-f]+) RDI: ([0-9a-f]+)/) { 70 if ($line =~ /RBP: ([0-9a-f]+) R08: ([0-9a-f]+) R09: ([0-9a-f]+)/) { 74 if ($line =~ /R10: ([0-9a-f]+) R11: ([0-9a-f]+) R12: ([0-9a-f]+)/) { 79 if ($line =~ /R13: ([0-9a-f]+) R14: ([0-9a-f]+) R15: ([0-9a-f]+)/) { 104 if ($line =~ /([0-9a-zA-Z\,\%\(\)\-\+]+)$/) { 116 $clobber =~ s/\([a-z0-9\%\,]+\)//g; 137 # we print it with a =>, and then delete its value [all …]
|
/openbmc/webui-vue/src/views/Settings/Network/ |
H A D | ModalIpv6.vue | 78 …a-fA-F0-9]{1,4}:){7}[a-fA-F0-9]{1,4}|(?:[a-fA-F0-9]{1,4}:){1,7}:|(?:[a-fA-F0-9]{1,4}:){1,6}:[a-fA-… 83 /^(12[0-8]|1[0-9]|[1-9][0-9]|[0-9])$/,
|
H A D | ModalDefaultGateway.vue | 60 …a-fA-F0-9]{1,4}:){7}[a-fA-F0-9]{1,4}|(?:[a-fA-F0-9]{1,4}:){1,7}:|(?:[a-fA-F0-9]{1,4}:){1,6}:[a-fA-…
|
/openbmc/linux/Documentation/filesystems/ |
H A D | 9p.rst | 4 v9fs: Plan 9 Resource Sharing for Linux 10 v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol. 19 the 9p client is available in the form of a USENIX paper: 29 * CellFS: A New Programming Model for the Cell BE 31 * PROSE I/O: Using 9p to enable Application Partitions 33 * VirtFS: A Virtualization Aware File System pass-through 41 mount -t 9p 10.10.1.2 /mnt/9 43 For Plan 9 From User Space applications (http://swtch.com/plan9):: 45 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER 49 mount -t 9p -o trans=virtio <mount_tag> /mnt/9 [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/linuxconsole/linuxconsole/ |
H A D | 51-these-are-not-joysticks-rm.rules | 7 SUBSYSTEM=="input", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c30a", KERNEL=="js[0-9]*", RUN+="/b… 9 SUBSYSTEM=="input", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a0df", KERNEL=="js[0-9]*", RUN+="/b… 10 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", ENV{ID_INPUT_JOYSTICK}=="?*"… 11 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0010", KERNEL=="js[0-9]*", RUN+="/b… 12 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", ENV{ID_INPUT_JOYSTICK}=="?*"… 13 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0011", KERNEL=="js[0-9]*", RUN+="/b… 14 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", ENV{ID_INPUT_JOYSTICK}=="?*"… 15 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0012", KERNEL=="js[0-9]*", RUN+="/b… 16 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0013", ENV{ID_INPUT_JOYSTICK}=="?*"… 17 SUBSYSTEM=="input", ATTRS{idVendor}=="056a", ATTRS{idProduct}=="0013", KERNEL=="js[0-9]*", RUN+="/b… [all …]
|
/openbmc/linux/include/net/9p/ |
H A D | 9p.h | 3 * 9P protocol definitions. 16 * @P9_DEBUG_9P: 9P protocol tracing 41 P9_DEBUG_FID = (1<<9), 62 * enum p9_msg_t - 9P message types 64 * @P9_RLERROR: response for any failed request for 9P2000.L 69 * @P9_TMKNOD: create a special file object request 70 * @P9_RMKNOD: create a special file object response 71 * @P9_TLCREATE: prepare a handle for I/O on an new file for 9P2000.L 72 * @P9_RLCREATE: response with file access information for 9P2000.L 75 * @P9_TMKDIR: create a directory request [all …]
|
/openbmc/bmcweb/redfish-core/schema/oem/openbmc/json-schema/ |
H A D | OpenBMCManager.v1_0_0.json | 11 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 12 "description": "This property shall specify a valid odata or Redfish property.", 87 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 88 "description": "This property shall specify a valid odata or Redfish property.", 211 "[A-Za-z0-9_.:]+": { 214 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 215 "description": "This property shall specify a valid odata or Redfish property.", 235 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 236 "description": "This property shall specify a valid odata or Redfish property.", 282 "[A-Za-z0-9_.:]+": { [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | AddressPool.v1_3_0.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 28 …shall contain the lower Autonomous System (AS) number to be used as part of a range of ASN values.… 37 …shall contain the upper Autonomous System (AS) number to be used as part of a range of ASN values.… 52 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 53 "description": "This property shall specify a valid odata or Redfish property.", 77 … "longDescription": "This resource shall represent an address pool in a Redfish implementation.", 79 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 80 "description": "This property shall specify a valid odata or Redfish property.", 169 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { [all …]
|
H A D | Event.v1_11_0.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 37 "description": "Details for a CPER section or record associated with an event.", 38 …"longDescription": "This object shall contain the details for a CPER section or record that is the… 40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 41 "description": "This property shall specify a valid odata or Redfish property.", 55 "description": "The CPER Notification Type for a CPER record.", 56 …ngDescription": "This property shall contain the CPER Notification Type for a CPER record that cor… 57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$", 73 …"longDescription": "This property shall contain the CPER Section Type for a CPER section that corr… [all …]
|
H A D | SwitchMetrics.v1_0_2.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 43 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 44 "description": "This property shall specify a valid odata or Redfish property.", 71 …on": "The memory metrics since the last switch reset or `ClearCurrentPeriod` action for a switch.", 72 …all describe the memory metrics since the last reset or `ClearCurrentPeriod` action for a switch.", 74 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 75 "description": "This property shall specify a valid odata or Redfish property.", 111 "description": "The memory metrics for a switch.", 112 …cription": "This property shall contain properties that describe the memory metrics for a switch.", [all …]
|
H A D | ComponentIntegrity.v1_3_0.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 46 "description": "This property shall specify a valid odata or Redfish property.", 61 … "description": "A link to the certificate that represents the identity of the component.", 62 …"longDescription": "This property shall contain a link to a resource of type `Certificate` that re… 86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 87 "description": "This property shall specify a valid odata or Redfish property.", 120 …egrity` resource provides critical and pertinent security information about a specific device, sys… 121 … resource shall represent critical and pertinent security information about a specific device, sys… [all …]
|
H A D | VCATEntry.v1_0_3.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 40 "description": "This property shall specify a valid odata or Redfish property.", 57 …an entry in a Virtual Channel Action Table. A Virtual Channel is a mechanism used to create multi… 58 … "This resource shall represent an entry of Virtual Channel Action Table in a Redfish implementati… 60 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 61 "description": "This property shall specify a valid odata or Redfish property.", 118 "pattern": "^0[xX](([a-fA-F]|[0-9])*)$", 144 …"description": "The Virtual Channel Action Table entry corresponding to a specific Virtual Channel… [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | nvidia,tegra210-ahub.yaml | 10 The Audio Hub (AHUB) comprises a collection of hardware accelerators 11 for audio pre-processing, post-processing and a programmable full 22 pattern: "^ahub@[0-9a-f]*$" 69 '^port@[0-9]': 74 '^i2s@[0-9a-f]+$': 77 '^dmic@[0-9a-f]+$': 81 '^admaif@[0-9a-f]+$': 85 '^dspk@[0-9a-f]+$': 89 '^mvc@[0-9a-f]+$': 93 '^sfc@[0-9a-f]+$': [all …]
|
/openbmc/qemu/tests/qtest/libqos/ |
H A D | virtio-9p-client.h | 2 * 9P network client for VirtIO 9P test cases (based on QTest) 11 * Not so fast! You might want to read the 9p developer docs first: 12 * https://wiki.qemu.org/Documentation/9p 18 #include "hw/9pfs/9p.h" 19 #include "hw/9pfs/9p-synth.h" 20 #include "virtio-9p.h" 24 #define P9_MAX_SIZE 4096 /* Max size of a T-message or R-message */ 76 /* options for 'Twalk' 9p request */ 78 /* 9P client being used (mandatory) */ 91 /* data being received from 9p server as 'Rwalk' response (optional) */ [all …]
|
/openbmc/openbmc/poky/meta/recipes-support/gpgme/gpgme/ |
H A D | 0001-pkgconfig.patch | 29 diff --git a/configure.ac b/configure.ac 31 --- a/configure.ac 41 diff --git a/src/Makefile.am b/src/Makefile.am 43 --- a/src/Makefile.am 59 diff --git a/src/gpgme-pthread.pc.in b/src/gpgme-pthread.pc.in 75 +Description: GnuPG Made Easy (GPGME) is a C language library that allows to addsupport for cryptog… 80 diff --git a/src/gpgme.m4 b/src/gpgme.m4 82 --- a/src/gpgme.m4 100 - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'` 102 - sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'` [all …]
|
/openbmc/u-boot/tools/scripts/ |
H A D | define2mk.sed | 10 /^#define CONFIG_[A-Za-z0-9_][A-Za-z0-9_]*/ { 24 s/="\([0-9][0-9]*\)"/=\1/; 26 s/="\(-[1-9][0-9]*\)"/=\1/; 28 s/="\(0[Xx][0-9a-fA-F][0-9a-fA-F]*\)"/=\1/; 30 s/="\(CONFIG_[A-Za-z0-9_][A-Za-z0-9_]*\)"/=$(\1)/;
|
/openbmc/linux/arch/powerpc/crypto/ |
H A D | aes-tab-4k.S | 10 * crypto/aes_generic.c and are designed to be simply accessed by a combination 11 * of rlwimi/lwz instructions with a minimum of table registers (usually only 19 * This is a quite good tradeoff for low power devices (e.g. routers) without 25 #define R(a, b, c, d) \ argument 26 0x##a##b##c##d, 0x##d##a##b##c, 0x##c##d##a##b, 0x##b##c##d##a 40 .long R(4d, ab, ab, e6), R(ec, 76, 76, 9a) 41 .long R(8f, ca, ca, 45), R(1f, 82, 82, 9d) 47 .long R(23, 9c, 9c, bf), R(53, a4, a4, f7) 48 .long R(e4, 72, 72, 96), R(9b, c0, c0, 5b) 50 .long R(3d, 93, 93, ae), R(4c, 26, 26, 6a) [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/mfd/ |
H A D | qcom,spmi-pmic.yaml | 14 each. A function can consume one or more of these fixed-size register regions. 17 PMICs. These PMICs use a "QPNP" scheme through SPMI interface. 18 QPNP is effectively a partitioning scheme for dividing the SPMI extended 30 - pattern: '^pm(a|s)?[0-9]*@.*$' 121 "^adc@[0-9a-f]+$": 128 "^adc-tm@[0-9a-f]+$": 132 "^audio-codec@[0-9a-f]+$": 136 "^charger@[0-9a-f]+$": 143 "gpio@[0-9a-f]+$": 147 "^led-controller@[0-9a-f]+$": [all …]
|
/openbmc/sdbusplus/tools/sdbusplus/schemas/ |
H A D | events.schema.yaml | 16 pattern: "^[0-9]+\\.[0-9]+\\.[0-9]+$" 30 pattern: "^[A-Z][A-Z0-9a-z]*$" 36 A description of the field for use by 84 pattern: "^E[A-Z0-9]+$" 105 A developer-applicable description of the error reported. 121 pattern: "^[A-Z_][a-zA-Z0-9_]*(\\.[A-Z_][a-zA-Z0-9_]*)*$" 122 description: Used when a `sdbusplus` event should map to a 123 specific Redfish Message rather than a generated one. This 124 is useful when an internal error has an analog in a 134 pattern: "^[0-9]+\\.[0-9]+\\.[0-9]+$"
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | Event.v1_11_0.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 37 "description": "Details for a CPER section or record associated with an event.", 38 …"longDescription": "This object shall contain the details for a CPER section or record that is the… 40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 41 "description": "This property shall specify a valid odata or Redfish property.", 55 "description": "The CPER Notification Type for a CPER record.", 56 …ngDescription": "This property shall contain the CPER Notification Type for a CPER record that cor… 57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$", 73 …"longDescription": "This property shall contain the CPER Section Type for a CPER section that corr… [all …]
|
H A D | ComponentIntegrity.v1_3_0.json | 12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 13 "description": "This property shall specify a valid odata or Redfish property.", 45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 46 "description": "This property shall specify a valid odata or Redfish property.", 61 … "description": "A link to the certificate that represents the identity of the component.", 62 …"longDescription": "This property shall contain a link to a resource of type `Certificate` that re… 86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 87 "description": "This property shall specify a valid odata or Redfish property.", 120 …egrity` resource provides critical and pertinent security information about a specific device, sys… 121 … resource shall represent critical and pertinent security information about a specific device, sys… [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/ssiapi/ssiapi/ |
H A D | 0001-Don-t-use-__GNUC_PREREQ.patch | 23 diff --git a/lib/efi/efi.h b/lib/efi/efi.h 25 --- a/lib/efi/efi.h 27 @@ -33,9 +33,9 @@ 39 diff --git a/lib/engine/pragma.h b/lib/engine/pragma.h 41 --- a/lib/engine/pragma.h 43 @@ -32,9 +32,9 @@ 55 diff --git a/lib/log/log.h b/lib/log/log.h 57 --- a/lib/log/log.h 59 @@ -32,9 +32,9 @@ 71 diff --git a/lib/mpb/machine_bytes.h b/lib/mpb/machine_bytes.h [all …]
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | common.filter | 12 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 15 # You should have received a copy of the GNU General Public License 24 sed -Ee 's/[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}/yyyy-mm-dd hh:mm:ss/' 29 sed -E -e 's/[0-9. ]{5} [KMGT]iB/ SIZE/' \ 30 -e 's/[0-9. ]{5} B/ SIZE/' 35 sed -Ee 's/\#block[0-9]{3,}/NODE_NAME/' 40 gsed -e '/Attached to:/s/\device[[0-9]\+\]/device[N]/g' 63 -e '/Image end offset: [0-9]\+/d' 76 …gsed -e "s/[0-9]* ops\; [0-9/:. sec]* ([0-9/.inf]* [EPTGMKiBbytes]*\/sec and [0-9/.inf]* ops\/sec)… 77 -e "s/: line [0-9][0-9]*: *[0-9][0-9]*\( Aborted\| Killed\)/:\1/" \ [all …]
|
/openbmc/bmcweb/test/include/ |
H A D | ossl_random.cpp | 21 "^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}$")); in TEST() 27 EXPECT_THAT(getRandomIdOfLength(1), MatchesRegex("^[a-zA-Z0-9]$")); in TEST() 28 EXPECT_THAT(getRandomIdOfLength(10), MatchesRegex("^[a-zA-Z0-9]{10}$")); in TEST()
|
/openbmc/linux/net/9p/ |
H A D | Kconfig | 3 # 9P protocol configuration 7 tristate "Plan 9 Resource Sharing Support (9P2000)" 10 Plan 9 resource sharing via the 9P2000 protocol. 22 tristate "9P FD Transport" 29 tristate "9P Virtio Transport" 31 This builds support for a transports between 32 guest partitions and a host partition. 37 tristate "9P Xen Transport" 39 This builds support for a transport for 9pfs between 45 tristate "9P RDMA Transport (Experimental)" [all …]
|