| /openbmc/docs/ |
| H A D | hw-vendor-repos-policy.md | 1 # Hardware Vendor Repository Policy
12 a request for a new repository or a bitbake recipe to be hosted under the
26 following requirements to be eligible for a repository under OpenBMC:
29 2. If an existing repository, it has an active maintainer
32 4. The new repository will not break others (i.e. providing new APIs utilized by
33 a common repository that are not protected by compile flags, etc)
37 - Reference: "Create a new repository" TOF [process][tof]
40 Note that the first option should always be to look into hosting the repository
41 under OpenBMC (vs. a recipe in OpenBMC that points to an external repository).
43 A repository must be hosted under OpenBMC if:
[all …]
|
| H A D | meta-layer-guidelines.md | 30 through a gerrit review, and follow the processes outlined for the repository.
92 bypass code review by pointing the upstream recipe to a public repository that
102 under the openbmc/openbmc repository where it can be reviewed, along with an
113 **What defines an OpenBMC specific repository?**
115 Generally an OpenBMC specific repository is something that does any of the
138 and/or discord. If the design would require a new repository, request one using
145 Repository branches can change at any time. Pointing to an autorev revision
155 Point SRCREV to a specific commit of the repository, and increase the revision
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | maint-appx.rst | 19 kernel repository (or tree) and accompanying Metadata in the
23 particular Yocto Project Linux kernel repository and use it to build
28 Linux kernel source repository and ``yocto-kernel-cache`` Git trees. For
37 how to set up a local Git repository of the Yocto Project Linux kernel
42 Once you have cloned the kernel Git repository and the cache of Metadata
44 in the repository using the following Git command::
50 "standard/beagleboard" branch of the Yocto Linux kernel repository and
51 the "yocto-4.12" branch of the ``yocto-kernel-cache`` repository::
60 Branches in the ``yocto-kernel-cache`` repository correspond to Yocto Linux
68 kernel, you need to examine the ``yocto-kernel-cache`` Git repository.
[all …]
|
| /openbmc/openbmc/poky/documentation/overview-manual/ |
| H A D | development-environment.rst | 151 repository for that particular item. Having a local Git repository of
160 repository, any supported BSP tarball, or Yocto Project tools. Unpacking
172 BSP repository and the Source Directory (i.e. ``poky``)
173 repository. For example, if you have checked out the "&DISTRO_NAME_NO_CAP;"
193 and extracting these files does not produce a local copy of a Git repository
233 repository. The development branch is the "upstream" repository from which
246 The Yocto Project ``poky`` Git repository also has an upstream
247 contribution Git repository named ``poky-contrib``. You can see all the
248 branches in this repository using the web interface of the
254 branches into the "master" branch of the Git repository.
[all …]
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | repository_test.cpp | 17 #include "extensions/openpower-pels/repository.hpp"
54 EXPECT_EQ(Repository::getPELFilename(0x12345678, date), in TEST_F()
57 EXPECT_EQ(Repository::getPELFilename(0xAABBCCDD, date), in TEST_F()
60 EXPECT_EQ(Repository::getPELFilename(0x3AFF1, date), in TEST_F()
63 EXPECT_EQ(Repository::getPELFilename(100, date), in TEST_F()
66 EXPECT_EQ(Repository::getPELFilename(0, date), "2030112813060708_00000000"); in TEST_F()
71 Repository repo{repoPath}; in TEST_F()
80 auto name = Repository::getPELFilename(pel->id(), ts); in TEST_F()
94 using pelID = Repository::LogID::Pel; in TEST_F()
95 using obmcID = Repository::LogID::Obmc; in TEST_F()
[all …]
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | repository.cpp | 16 #include "repository.hpp"
61 Repository::Repository(const std::filesystem::path& basePath, size_t repoSize, in Repository() function in openpower::pels::Repository
79 void Repository::restore() in restore()
160 std::string Repository::getPELFilename(uint32_t pelID, const BCDTime& time) in getPELFilename()
169 void Repository::add(std::unique_ptr<PEL>& pel) in add()
204 void Repository::write(const PEL& pel, const fs::path& path) in write()
236 std::optional<Repository::LogID> Repository::remove(const LogID& id) in remove()
248 "Removing PEL from repository, PEL ID = {PEL_ID}, BMC log ID = {BMC_ID}", in remove()
274 std::optional<std::vector<uint8_t>> Repository::getPELData(const LogID& id) in getPELData()
296 std::optional<sdbusplus::message::unix_fd> Repository::getPELFD(const LogID& id) in getPELFD()
[all …]
|
| H A D | repository.hpp | 17 * @class Repository
21 class Repository class
117 * of different types in the repository.
135 Repository() = delete;
136 ~Repository() = default;
137 Repository(const Repository&) = default;
138 Repository& operator=(const Repository&) = default;
139 Repository(Repository&&) = default;
140 Repository& operator=(Repository&&) = default;
145 * @param[in] basePath - the base filesystem path for the repository
[all …]
|
| H A D | host_notifier.hpp | 5 #include "repository.hpp"
21 * It uses the Repository class's subscription feature to be
61 * @param[in] repo - The PEL repository object
65 HostNotifier(Repository& repo, DataInterfaceBase& dataIface,
152 * Ideally this will never happen, as the Repository
163 * @brief This function gets called by the Repository class
175 * @brief This function gets called by the Repository class
191 * @return bool - This is an indicator to the Repository::for_each
276 * @brief The PEL repository object
278 Repository& _repo;
|
| /openbmc/linux/ |
| H A D | opengrok1.0.log | 1 2024-12-28 20:07:11.902-0600 FINER t583 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/linux',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/linux/drivers/net/ethernet/marvell/mvpp2/mvpp2_prs.c'
3 2024-12-28 20:07:11.899-0600 FINER t593 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/linux',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/linux/tools/testing/selftests/powerpc/tm/tm-signal-pagefault.c'
6 2024-12-28 20:07:11.896-0600 FINER t586 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/linux',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/linux/arch/powerpc/platforms/pasemi/idle.c'
8 2024-12-28 20:07:11.895-0600 FINER t584 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/openbmc',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/grilo/grilo_0.3.16.bb'
9 2024-12-28 20:07:11.894-0600 FINER t582 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/linux',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/linux/tools/perf/pmu-events/arch/powerpc/power8/cache.json'
11 2024-12-28 20:07:11.893-0600 FINER t589 IndexDatabase.createAnnotationCache: failed to create annotation: repository {dir='/opengrok/src/openbmc/qemu',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} does not allow to create annotation cache for '/opengrok/src/openbmc/qemu/include/qom/qom-qobject.h'
25 2024-12-28 20:07:11.915-0600 FINER t586 HistoryGuru.storeHistory: repository {dir='/opengrok/src/openbmc/u-boot',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} supports history for directories, skipping '/opengrok/src/openbmc/u-boot/drivers/net/lan91c96.h'
30 2024-12-28 20:07:11.916-0600 FINER t582 HistoryGuru.storeHistory: repository {dir='/opengrok/src/openbmc/libcper',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} supports history for directories, skipping '/opengrok/src/openbmc/libcper/sections/cper-section-firmware.c'
31 2024-12-28 20:07:11.916-0600 FINER t590 HistoryGuru.storeHistory: repository {dir='/opengrok/src/openbmc/linux',type=git,historyCache=on,renamed=false,merge=true,annotationCache=off} supports history for directories, skipping '/opengrok/src/openbmc/linux/drivers/phy/tegra/Kconfig'
32 2024-12-28 20:07:11.916-0600 FINER t584 HistoryGuru.storeHistory: repository {di
[all...] |
| H A D | opengrok0.0.log | [all...] |
| /openbmc/openbmc-test-automation/tools/ |
| H A D | github_issues_to_csv | 6 from a repository that username has access to. Supports GitHub API v3.
71 name Name of the GitHub repository
72 response GitHub repository response
100 description="Write GitHub repository issues to CSV file."
110 help="Repository names, formatted as 'basereponame/repo'",
130 for repository in args.repositories:
131 csvfilename_temp = "{}".format(repository.replace("/", "-"))
149 for repository in args.repositories:
151 l_url = l_url.format(repository, states)
154 get_issues_from_github_to_csv(repository, response)
|
| /openbmc/openbmc-tools/ |
| H A D | README.md | 3 The goal of this repository is to collect the two-minute hacks you write to
9 ## Repository Rules
16 Then this repository aims to be the default destination for your otherwise
22 Please use gerrit for all patches to this repository:
24 - [Gerrit](https://gerrit.openbmc-project.xyz/) Repository
42 ## How you consume the repository
45 the repository to your PATH might be a bit of a dice-roll. We may also move or
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_inband_sdr.robot | 6 ... 3. Reserve Device SDR Repository,
175 Verify Reserve Device SDR Repository Via Inband IPMI
176 [Documentation] Verify Reserve Device SDR Repository via inband IPMI.
179 # Reserve Device SDR Repository via inband IPMI.
180 ${resp}= Get Reserve Device SDR Repository
188 Verify Reserve Device SDR Repository For Invalid Data Request
189 [Documentation] Verify Reserve Device SDR Repository via inband IPMI with extra request bytes.
192 # Reserve Device SDR Repository with extra request bytes.
200 Verify Reserve Device SDR Repository Info Via IPMI Lanplus
201 [Documentation] Verify whether Reserve Device SDR Repository command is accessible via lanplus.
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | gomod.py | 5 from a module proxy or directly from a version control repository.
32 The method used when fetching directly from a version control repository.
36 The URL when fetching directly from a version control repository. Required
41 repository. Alternatively, set the SRCREV varible for "module@version".
45 repository. Required when the module is not located in the root of the
46 repository.
154 """Class to fetch Go modules directly from a git repository"""
161 """Set up to download the module from the git repository.
163 Set up to download the git repository to the module cache directory and
166 cache/vcs/<hash>: The bare git repository.
[all …]
|
| /openbmc/openbmc/poky/ |
| H A D | README.poky.md | 43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
|
| H A D | README.md | 43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
|
| /openbmc/openbmc/poky/meta-poky/ |
| H A D | README.poky.md | 43 As Poky is an integration repository (built using a tool called combo-layer),
49 - Git repository: <https://git.openembedded.org/openembedded-core/>
54 - Git repository: <https://git.openembedded.org/bitbake/>
59 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/>
64 - Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto>
67 If in doubt, check the openembedded-core git repository for the content you
70 git repository branch in question.
|
| /openbmc/docs/security/ |
| H A D | how-to-report-a-security-vulnerability.md | 18 - If you know which source code repository is affected, find the repository
28 separate owners. If you do not know which repository is affected, the owner or
32 security advisory][] in their repository and begin work. The advisory has draft
60 - If the problem is not severe, please write an issue to the affected repository
76 …https://docs.github.com/en/code-security/repository-security-advisories/creating-a-repository-secu…
|
| /openbmc/qemu/.gitlab-ci.d/cirrus/ |
| H A D | README.rst | 14 builds to happen when you push to your GitLab repository, you need to
16 * set up a GitHub repository for the project, eg. ``yourusername/qemu``.
17 This repository needs to exist for cirrus-run to work, but it doesn't need to
34 repository, create two new variables:
36 * ``CIRRUS_GITHUB_REPO``, containing the name of the GitHub repository
48 repository as usual and you'll automatically get the additional CI coverage.
|
| /openbmc/linux/arch/powerpc/platforms/ps3/ |
| H A D | platform.h | 65 /* repository bus info */
89 /* repository bus device info */
123 /* repository bus enumerators */
146 /* repository block device info */
170 /* repository logical pu and memory info */
209 /* repository pme info */
217 /* repository performance monitor info */
222 /* repository 'Other OS' area */
228 /* repository spu info */
248 /* repository vuart info */
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | start.rst | 331 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
426 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`"
591 repository at :yocto_git:`/poky`.
594 ``poky`` Git repository:
600 #. *Select the Repository:* Click on the repository in which you are
603 #. *Find the URL Used to Clone the Repository:* At the bottom of the
604 page, note the URL used to clone that repository
609 For information on cloning a repository, see the
610 ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" section.
627 use Git to clone the upstream repository and work from within that
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
| H A D | socorro-syms.bbclass | 66 # Go through all references and replace the file paths with repository
87 # If the file could be found in any repository then replace it with the
88 # repository's path.
100 # Check which VCS is used and use that to extract repository information.
104 # Make sure the git repository we just found wasn't the yocto repository
105 # itself, i.e. the root of the repository we're looking for must be a
175 # path up to and including the repository's root directory, e.g. remove
185 # Assemble the repository path according to the Socorro format.
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | importlayer.html | 54 The <span class="dup-layer-name"></span> repository url is
82 In a <strong>Git repository</strong>
84 … radio-help">To build the layer Toaster must be able to access the Git repository, otherwise build…
95 <legend>Git repository information</legend>
98 Git repository URL
99 …phicon glyphicon-question-sign get-help" title="Fetch/clone URL of the repository. Currently, Toas…
105 Repository subdirectory
107 …tle="Subdirectory within the repository where the layer is located, if not in the root (usually on…
152 …lign: middle;">To import a layer you need to enter a layer name, a Git repository URL and a Git re…
|
| /openbmc/openpower-host-ipmi-oem/ |
| H A D | OWNERS | 5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
|
| /openbmc/ibm-logging/ |
| H A D | OWNERS | 5 # parts of this repository, including code review and approval. We use the
12 # An OWNERS file must be in the root of a repository but may also be present
18 # repository.
21 # on the repository.
|