Home
last modified time | relevance | path

Searched refs:JSON (Results 1 – 25 of 293) sorted by relevance

12345678910>>...12

/openbmc/bmcweb/test/include/
H A Dhttp_utility_test.cpp21 isContentTypeAllowed("application/json", ContentType::JSON, false)); in TEST()
33 isContentTypeAllowed("application/html", ContentType::JSON, false)); in TEST()
61 std::array<ContentType, 2> htmlJson{ContentType::HTML, ContentType::JSON}; in TEST()
77 std::array<ContentType, 2> jsonHtml{ContentType::JSON, ContentType::HTML}; in TEST()
81 std::array<ContentType, 2> cborJson{ContentType::CBOR, ContentType::JSON}; in TEST()
88 ContentType::JSON); in TEST()
96 ContentType::JSON); in TEST()
102 ContentType::JSON); in TEST()
106 ContentType::JSON); in TEST()
111 ContentType::JSON); in TEST()
[all …]
/openbmc/phosphor-webui/app/common/services/
H A Dapi-utils.js38 console.log(JSON.stringify(error));
66 console.log(JSON.stringify(error));
87 data: JSON.stringify({'data': []})
103 var json = JSON.stringify(response.data);
104 var content = JSON.parse(json);
133 var data = JSON.stringify({
141 var content = JSON.parse(evt.data);
169 var data = JSON.stringify({
181 var content = JSON.parse(evt.data);
215 var data = JSON.stringify({
[all …]
/openbmc/phosphor-power/phosphor-regulators/test/
H A Dffdc_file_tests.cpp49 FFDCFile file{FFDCFormat::JSON}; in TEST()
52 EXPECT_EQ(file.getFormat(), FFDCFormat::JSON); in TEST()
76 FFDCFile file{FFDCFormat::JSON}; in TEST()
115 FFDCFile file{FFDCFormat::JSON}; in TEST()
124 FFDCFile file{FFDCFormat::JSON}; in TEST()
139 FFDCFile file{FFDCFormat::JSON}; in TEST()
154 FFDCFile file{FFDCFormat::JSON}; in TEST()
173 FFDCFile file{FFDCFormat::JSON}; in TEST()
188 FFDCFile file{FFDCFormat::JSON}; in TEST()
209 FFDCFile file{FFDCFormat::JSON}; in TEST()
/openbmc/phosphor-webui/app/configuration/controllers/
H A Dnetwork-controller.js35 $scope.oldInterface = JSON.parse(JSON.stringify($scope.interface));
176 console.log(JSON.stringify(error));
186 console.log(JSON.stringify(error));
196 console.log(JSON.stringify(error));
208 console.log(JSON.stringify(error));
220 console.log(JSON.stringify(error));
231 console.log(JSON.stringify(error));
247 console.log(JSON.stringify(error));
270 console.log(JSON.stringify(error));
275 console.log(JSON.stringify(error));
[all …]
/openbmc/libcper/
H A DREADME.md1 # CPER JSON Representation & Conversion Library
4 described in UEFI Specification Appendix N) in a human-readable JSON format, in
6 standard CPER binary format and the specified structured JSON.
25 CPER-JSON. The first of these is `cper-convert`, which is a command line tool
27 CPER-JSON through the command line. An example usage scenario is below:
45 Finally, a static library containing symbols for converting CPER and CPER-JSON
46 between an intermediate JSON format can be found generated at
56 The specification for this project's CPER-JSON format can be found in
57 `specification/`, defined in both JSON Schema format and also as a LaTeX
65 between a SatMC and OpenBMC board, including a conversion into CPER JSON for
/openbmc/linux/tools/perf/pmu-events/arch/powerpc/
H A Dmapfile.csv2 # PVR,Version,JSON/file/pathname,Type
6 # Version could be used to track version of of JSON file
8 # JSON/file/pathname is the path to JSON file, relative
12 # Multiple PVRs could map to a single JSON file.
/openbmc/phosphor-webui/app/overview/controllers/
H A Dsystem-overview-controller.js41 console.log(JSON.stringify(error));
50 console.log(JSON.stringify(error));
62 console.log(JSON.stringify(error));
70 console.log(JSON.stringify(error));
78 console.log(JSON.stringify(error));
86 console.log(JSON.stringify(error));
99 console.log(JSON.stringify(error));
110 console.log(JSON.stringify(error));
/openbmc/openbmc/poky/meta/recipes-devtools/json-c/
H A Djson-c_0.18.bb1 SUMMARY = "A JSON implementation in C"
2 DESCRIPTION = "JSON-C implements a reference counting object model that allows \
3 you to easily construct JSON objects in C, output them as JSON formatted strings \
4 and parse JSON formatted strings back into the C representation of JSON objects."
/openbmc/openbmc/poky/meta/recipes-gnome/json-glib/
H A Djson-glib_1.10.6.bb1 SUMMARY = "JSON-GLib implements a full JSON parser using GLib and GObject"
2 DESCRIPTION = "Use JSON-GLib it is possible to parse and generate valid JSON\
3 data structures, using a DOM-like API. JSON-GLib also offers GObject \
5 instances to and from JSON data types."
/openbmc/openbmc-tools/expectedJsonChecker/
H A DREADME.md1 # Expected JSON Checker tool
3 A tool that cross checks an expected set of JSON entries, by a given index, with
4 a given input set of JSON entries. In addition, there's an ability to filter
6 contain JSON entries. This filtering functionality on cross checking expected
9 Expected entries that only want to be found within the input JSON should use a
16 entries within the BMC's enumerated sensor JSON output against an expected set
19 machine's enumerated sensor data and inventory data to separate JSON files, an
21 created for this machine. These JSON files are then fed into this tool to
23 The machine's name was used as the index into the expected JSON to allow the
24 same expected JSON file to be used across multiple machines instead of having
[all …]
/openbmc/linux/tools/perf/pmu-events/arch/nds32/
H A Dmapfile.csv2 # MIDR,Version,JSON/file/pathname,Type
7 # Version could be used to track version of of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/perl/
H A Dlibjson-perl_4.03000.bb2 DESCRIPTION = "This package contains the JSON.pm module with friends. \
3 The module implements JSON encode/decode."
5 HOMEPAGE = "https://metacpan.org/pod/JSON"
12 SRC_URI = "git://github.com/makamaka/JSON.git;protocol=https;branch=master"
/openbmc/linux/tools/perf/pmu-events/arch/riscv/
H A Dmapfile.csv2 # MVENDORID-MARCHID-MIMPID,Version,JSON/file/pathname,Type
9 # Version could be used to track version of JSON file
11 # JSON/file/pathname is the path to JSON file, relative
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-spirit/
H A Djson-spirit_4.08.bb1 SUMMARY = "A C++ JSON Parser/Generator Implemented with Boost Spirit."
2 DESCRIPTION = "JSON Spirit, a C++ library that reads and writes JSON files or streams. \
4 already using Boost, you can use JSON Spirit without any additional \
/openbmc/openbmc/meta-arm/ci/
H A Djunit.sh11 JSON=$BUILDDIR/tmp/log/oeqa/testresults.json
13 if test -f $JSON; then
14 resulttool junit $JSON
/openbmc/linux/tools/perf/pmu-events/
H A DREADME8 The 'jevents' program tries to locate and process JSON files in the directory
12 JSON files, each of which describes a set of PMU events.
19 - To reduce JSON event duplication per architecture, platform JSONs may
27 should be placed in a separate JSON file - where the file name identifies
30 All the topic JSON files for a CPU model/family should be in a separate
41 Using the JSON files and the mapfile, 'jevents' generates the C source file,
45 (one table like the following, per JSON file; table name 'pme_power8'
46 is derived from JSON file name, 'power8.json').
80 JSON file. Hence several entries in the pmu_events_map[] could map
137 is the pathname to the directory containing the CPU's JSON
[all …]
/openbmc/phosphor-webui/app/server-control/controllers/
H A Dpower-usage-controller.js28 console.log(JSON.stringify(error));
36 console.log(JSON.stringify(error));
83 console.log(JSON.stringify(error));
93 console.log(JSON.stringify(error));
/openbmc/phosphor-webui/app/access-control/controllers/
H A Duser-controller.js82 console.log(JSON.stringify(error));
99 console.log(JSON.stringify(error));
113 console.log(JSON.stringify(error));
130 console.log(JSON.stringify(error));
152 console.log(JSON.stringify(error));
179 console.log(JSON.stringify(error));
216 console.log(JSON.stringify(error));
250 console.log(JSON.stringify(error));
/openbmc/phosphor-fan-presence/
H A DREADME.md21 By default, runtime JSON configuration file(s) are used for each application.
22 The use of YAML configuration file(s) has been deprecated in favor of the JSON
24 once all applications completely support getting their configuration from JSON
73 Meson defaults to JSON based runtime configuration, so to select the YAML
79 ### JSON subsection
83 each using JSON.
85 As JSON based runtime configuration is the default option, no extra options are
92 supported using the JSON based configuration are listed below:**
101 - [Sensor Monitoring](#sensor-monitoring) - Only supports JSON
134 #### JSON subsubsection
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/
H A DREADME.md6 the power sequencer device. The application is configured by an optional JSON
11 - [config_files](config_files/) contains JSON configuration files
12 - [docs](docs/) contains documentation on this application and the JSON
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/
H A Dyajl_1.0.12.bb1 SUMMARY = "Yet Another JSON Library."
3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
4 written in ANSI C, and a small validating JSON generator."
H A Dyajl_2.1.0.bb1 SUMMARY = "Yet Another JSON Library."
3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
4 written in ANSI C, and a small validating JSON generator."
/openbmc/openbmc/poky/meta/recipes-devtools/python/
H A Dpython3-jsonschema-specifications_2024.10.1.bb1 SUMMARY = "The JSON Schema meta-schemas and vocabularies, exposed as a Registry"
2 DESCRIPTION = "JSON support files from the JSON Schema Specifications (metaschemas, \
/openbmc/pldm/tools/fw-update/
H A DREADME.md21 metadatafile Path of metadata JSON file
27 - Providing the metadata JSON file is a must
33 ## Metadata JSON file
37 in JSON format. Typically it is not necessary to write this file each time the
39 metadata JSON files can be reused. The key names used in the metadata JSON
50 - whether those fields need to be specified in the JSON, or are generated by the
55 Metadata JSON must have a key called "PackageHeaderInformation", which is of
74 Metadata JSON must have a key called "FirmwareDeviceIdentificationArea", which
94 - RecordDescriptors: Metadata JSON must have a key called "Descriptors", which
127 Metadata JSON must have a key called "ComponentImageInformationArea", which is
/openbmc/linux/tools/testing/selftests/bpf/
H A Dtest_offload.py143 def tool(name, args, flags, JSON=True, ns="", fail=True, include_stderr=False): argument
145 if JSON:
158 if JSON and len(stdout.strip()) != 0:
168 def bpftool(args, JSON=True, ns="", fail=True, include_stderr=False): argument
169 return tool("bpftool", args, {"json":"-p"}, JSON=JSON, ns=ns,
173 _, progs = bpftool("prog show", JSON=True, ns=ns, fail=True)
185 _, maps = bpftool("map show", JSON=True, ns=ns, fail=True)
225 def ip(args, force=False, JSON=True, ns="", fail=True, include_stderr=False): argument
228 return tool("ip", args, {"json":"-j"}, JSON=JSON, ns=ns,
231 def tc(args, JSON=True, ns="", fail=True, include_stderr=False): argument
[all …]

12345678910>>...12