#
4954d029 |
| 17-Jun-2024 |
Manojkiran Eda <manojkiran.eda@gmail.com> |
Fix spelling mistakes using codespell
This commit corrects various spelling mistakes throughout the repository. The corrections were made automatically using `codespell`[1] tool.
[1]: https://githu
Fix spelling mistakes using codespell
This commit corrects various spelling mistakes throughout the repository. The corrections were made automatically using `codespell`[1] tool.
[1]: https://github.com/codespell-project/codespell
Change-Id: I3b65183bab2be7aab90d1e184eb778216a54c145 Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
show more ...
|
#
b4edc27a |
| 19-Jul-2022 |
Andrew Geissler <geissonator@yahoo.com> |
utilize "/usr/bin/env perl" in perl scripts
When utilizing /usr/bin/perl, this expands to the full path of your filesystem build. i.e. something like this:
/home/andrewg/Code/openbmc/build/withersp
utilize "/usr/bin/env perl" in perl scripts
When utilizing /usr/bin/perl, this expands to the full path of your filesystem build. i.e. something like this:
/home/andrewg/Code/openbmc/build/witherspoon/tmp/work/x86_64-linux/mrw-perl-tools-native/1.0+gitAUTOINC+65ca8e19c4-r1/recipe-sysroot-native/usr/bin/perl
This now exceeds the allowed size by yocto: "maximum shebang size exceeded, the maximum size is 128."
There are ways to disable this check in yocto, and we probably have a case to argue this upstream, but our use in OpenBMC of perl is pretty limited so the easiest solution is to just move the perl scripts over to using /usr/bin/env. Half the perl scripts in this repo already do this.
Tested: - Verified new yocto now builds this repo
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I1c6dfc49a9a1d5ace0d0b9fdd4fa7a0abdee033e
show more ...
|
#
65ca8e19 |
| 16-Jul-2022 |
Andrew Geissler <geissonator@yahoo.com> |
ensure no space in script type string
New bitbake checks to ensure the #! line does not exceed 180 characters and it requires no space between it and the script type info.
Signed-off-by: Andrew Gei
ensure no space in script type string
New bitbake checks to ensure the #! line does not exceed 180 characters and it requires no space between it and the script type info.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: If52da98c06aced381a6b82cfc0756c1a322f7aec
show more ...
|
#
51041fc8 |
| 08-Oct-2019 |
Santosh Puranik <santosh.puranik@in.ibm.com> |
IPMI Parser Script Updates
This commit adds a new option to the IPMI MRW parsing scripts (--skip-broken-mrw).
When specified, the option will cause the scripts to ignore broken MRW targets such as
IPMI Parser Script Updates
This commit adds a new option to the IPMI MRW parsing scripts (--skip-broken-mrw).
When specified, the option will cause the scripts to ignore broken MRW targets such as IPMI sensor targets without a valid SENSOR_ID attribute or a FRU without a valid FRU_ID.
This allows us to pull in an in-progress MRW without it breaking our builds.
Tested: I tested the scripts against an incomplete MRW and made sure that the scripts ignored broken targets and generated output config files for whatever targets were valid.
Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: Ibf2ca3769e6030d62e73fb362d73a775433273bc
show more ...
|
#
8b34b33f |
| 24-Jan-2018 |
Ratan Gupta <ratagupt@in.ibm.com> |
Add entityID and entityInstance in the generated YAML
EntityID will be given by the config yaml and unique instance id would be generated for each entityID. eg: if proc is having entityID is x and i
Add entityID and entityInstance in the generated YAML
EntityID will be given by the config yaml and unique instance id would be generated for each entityID. eg: if proc is having entityID is x and if there is y instances of type x then this commit would generate y unique id for type x.
Change-Id: Ie7d848d96a6f335999eb226a4267b347f0e4ab2b Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
show more ...
|
#
d92101d5 |
| 15-Feb-2017 |
Ratan Gupta <ratagupt@in.ibm.com> |
Inventory: Implementing the association of objects.
This script will look at the associated types in the config file and make the association.
Change-Id: I25bafb1308bbcb1febc2c24d8154643a1f154cdb S
Inventory: Implementing the association of objects.
This script will look at the associated types in the config file and make the association.
Change-Id: I25bafb1308bbcb1febc2c24d8154643a1f154cdb Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
show more ...
|
#
6225e93d |
| 07-Feb-2017 |
Deepak Kodihalli <dkodihal@in.ibm.com> |
gen_openpower_fru.pl : Fetch inventory paths
In preparation for the openpower-vpd-parser recipe, this script will, from an input openpower vpd-config YAML file, determine which inventory objects we'
gen_openpower_fru.pl : Fetch inventory paths
In preparation for the openpower-vpd-parser recipe, this script will, from an input openpower vpd-config YAML file, determine which inventory objects we're interested in, and will fetch from the MRW pathnames these objects should have.
The script will output a file in a format that can serve as an environment file for a systemd service, which in turn will launch the openpower-vpd-parser application with this information.
Change-Id: I7c4fa70af002f63bd5501093802c1d41bd503e88 Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
show more ...
|
#
550075b1 |
| 30-Jan-2017 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
ipmi-fru-parser: Use YAML::TINY
YAML::XS is not required and not available.
Change-Id: Ia0250c08ff72dfc067291719183833fdb4204d03 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
#
26cc055b |
| 16-Jan-2017 |
Ratan Gupta <ratagupt@in.ibm.com> |
gen_ipmi_fru.pl : retrieve children of FRUs
For IPMI FRUs, figure out if they have children (non-FRU) that are of interest, and if yes, generate metadata for those children.
Change-Id: Iecc54dd3963
gen_ipmi_fru.pl : retrieve children of FRUs
For IPMI FRUs, figure out if they have children (non-FRU) that are of interest, and if yes, generate metadata for those children.
Change-Id: Iecc54dd39633f869b2210de83df9cb3292ab483a Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
show more ...
|
#
a149ba10 |
| 16-Jan-2017 |
Ratan Gupta <ratagupt@in.ibm.com> |
gen_ipmi_fru.pl: construct FRU metadata
For IPMI FRUs, generate a file to depict which dbus properties are implemented for a FRU, and what IPMI FRU properties those dbus properties map to.
This com
gen_ipmi_fru.pl: construct FRU metadata
For IPMI FRUs, generate a file to depict which dbus properties are implemented for a FRU, and what IPMI FRU properties those dbus properties map to.
This commit defines a YAML file which helps figure out the supported dbus inteface/properties for a FRU, and what the corresponding IPMI FRU properties are.
Change-Id: I26de1aa26e3a74fd8cc95bb0d479d9b036eb5683 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
show more ...
|
#
fa70dc9d |
| 16-Jan-2017 |
Ratan Gupta <ratagupt@in.ibm.com> |
gen_ipmi_fru.pl : Fetch FRU information from MRW
This commit serves as a building block since the script can now just print certain attributes (see output example below) for FRU elements defined in
gen_ipmi_fru.pl : Fetch FRU information from MRW
This commit serves as a building block since the script can now just print certain attributes (see output example below) for FRU elements defined in the MRW.
Typically, FRUs of interest to IPMI will have a non-zero FRU id defined.
Output example: FRUID => 1, FRUType => SYS, ObjectPath => /system FRUID => 2, FRUType => NODE, ObjectPath => /system/chassis
Change-Id: I3f27f905b2a366277e8a6120142c3fb136a44ad5 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
show more ...
|