| /openbmc/qemu/docs/devel/ |
| H A D | maintainers.rst | 7 They come from a wide range of backgrounds from unpaid hobbyists
16 They are also human and subject to the same pressures as everyone else
17 including overload and burnout. Like everyone else they are subject
45 - It has a maintainer but they don't have time to do
53 it does not mean they are paid to support you. This is open source and
76 asked by others to keep an eye on an area of code. They have generally
78 reviews, that they have a good understanding of the subsystem. They
96 GPG is used to sign pull requests so they can be identified as really
|
| H A D | kconfig.rst | 11 card, even though the boards use different PCI host bridges, and they
26 to list the components they need, and the compiled executable will
52 symbols; they are only visible in the Makefile. Each configurable component
56 falsehood is written ``n``. They are defined in a Kconfig
113 if more than one default is present, they will have different
148 Subsystems always default to false (they have no ``default`` directive)
150 up to other symbols to ``select`` whatever subsystems they require.
152 They sometimes have ``select`` directives to bring in other required
166 Devices are the most complex of the five. They can have a variety
170 Devices *depend on* the bus that they lie on, for example a PCI
[all …]
|
| H A D | code-provenance.rst | 10 patch submissions they make to the project. To put it another way,
11 contributors must indicate that they are legally permitted to contribute to
62 If the person sending the mail is not one of the patch authors, they are
73 * The non-primary author's contributions were so trivial that they can be
93 When multiple ``Signed-off-by`` tags are present, they should be strictly kept
103 mailing list, if they consider the patch acceptable, they should send an
105 review a patch should add this even if they are also adding their
110 queue it and send a pull request, they would send a mail containing a
113 maintainer wants to indicate they have done a full review they should use
117 behaviour of the patch in some manner, they should send an email reply
[all …]
|
| H A D | loads-stores.rst | 21 to guest ram or a local buffer). They deal with doing accesses
90 function call. They should therefore only be used in code that is
206 This means they must only be used from helper functions where the
275 any actions required by any tracing plugins. They are only to be
307 they perform accesses by guest virtual address, with a given ``MemOpIdx``.
309 They differ from ``cpu_{ld,st}_mmu`` in that they take the endianness
336 or device memory accesses. They take an AddressSpace, which is the
338 (They generally correspond to being the "master" end of a hardware bus
343 for the Secure world and one for NonSecure if they implement TrustZone).
348 modelling that they have an AddressSpace of their own.)
[all …]
|
| H A D | multiple-iothreads.rst | 18 same event loop, which monitors their file descriptors until they become
26 not shared completely. Sometimes it is useful to remember that although they
27 are conceptually similar they are currently not interchangeable.
73 Since they implicitly work on the main loop they cannot be used in code that
74 runs in an ``IOThread``. They might cause a crash or deadlock if called from an
104 are thread-safe. They can be used to trigger activity in an ``IOThread``.
|
| /openbmc/entity-manager/configurations/ |
| H A D | VENDORS.md | 3 To simplify the organization and ownership of configuration files, they can be
23 which they exclusively label and sell, such as a server chassis, they are the
37 claims to be the vendor of a device, they probably are, unless there is strong
38 evidence they are not.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 7 used in numerous products. They assemble multiple other open-source projects,
88 vulnerability reports before they are released.
112 are individuals selected by merit and do not represent the companies they work
113 for. They do not share information about confidential issues outside of the team
123 vulnerability, they quickly analyze and notify the reporter of the result.
124 They might also request more information.
126 If the issue is confirmed and affects the code maintained by the YP, they
132 If they deem it a real security problem in their software, they develop and
133 release a fix following their security policy. They may want to include the
147 problem. If they deem it a real security problem in their software, they
[all …]
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | gobject-introspection.bbclass | 10 # host's python 3 (they need to be run with native python 3)
23 # Define g-i options such that they can be disabled completely when GIR_MESON_OPTION is empty
58 # .typelib files are needed at runtime and so they go to the main package (so
59 # they'll be together with libraries they support).
62 # .gir files go to dev package, as they're needed for developing (but not for
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
| H A D | firmware_handler.cpp | 140 /* They are requesting information about the generic blob_id. */ in stat()
310 /* 2a) are they opening the active image? this can only happen if they in open()
313 /* 2b) are they opening the active hash? this can only happen if they in open()
319 /* Check that they've opened for writing - read back not currently in open()
327 /* Because canHandleBlob is called before open, we know that if they try to in open()
328 * open the verifyBlobId, they're in a state where it's present. in open()
341 * aren't open because of the fileOpen() check. They can still open in open()
363 /* When in this state, they can only open the updateBlobId */ in open()
385 /* To support multiple firmware options, we need to make sure they're in open()
386 * opening the one they already opened during this update sequence, or it's in open()
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Vim | 3 …m except that they must include this license text. You can also distribute unmodified parts of Vim…
11 …they will be distributed is negotiable. If there has been no negotiation then this license, or a l…
30 …ay use this license for previous Vim releases instead of the license that they came with, at your …
|
| H A D | psutils | 21 They may be copied and used for any purpose (including distribution as part of a for-profit product…
25 … Perl 4 kit). The GPL and Artistic License in NO WAY affect this license; they are merely used as …
29 …he programs so long as you acknowledge the author, and give people the originals if they want them.
|
| H A D | PDDL-1.0 | 16 …they have allowed anyone to use the work in whatever way they choose. Rightsholders therefore can’…
20 …They can do this because this document refers to the "Work", which can be either - or both - the d…
74 Users of this Database are cautioned that they may have to clear other rights or consult other lice…
86 …nd future rights in the Work under Copyright and Database Rights, whether they are vested or conti…
116 … that the Rightsholder may own. Users of this Database are cautioned that they may have to clear o…
118 …lder may use to cover the Work. Users of this Database are cautioned that they may have to clear o…
|
| /openbmc/u-boot/scripts/kconfig/tests/new_choice_with_dep/ |
| H A D | __init__.py | 2 Ask new choice values when they become visible.
4 If new choice values are added with new dependency, and they become
|
| /openbmc/qemu/docs/system/ |
| H A D | images.rst | 31 read only. When sectors in written, they are written in a temporary file
74 you can always make VM snapshots, but they are deleted as soon as you
79 - They cannot cope with removable devices if they are removed or
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/bluez5/bluez5/ |
| H A D | 0001-bluez5-disable-aics-tests.patch | 9 Temporarily disable aics tests as they can fail
10 depending on how the tests are executed. Sometimes they pass,
11 sometimes they fail. The issue has been observed since BlueZ 5.72 to 5.80
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | README.msl.md | 13 the value of the setting however they choose.
16 if they are of a certain revision or part, and taking some action if they are
|
| /openbmc/openbmc/poky/meta/recipes-support/ca-certificates/ca-certificates/ |
| H A D | 0003-update-ca-certificates-use-relative-symlinks-from-ET.patch | 19 time, they thusly all point into the host's file system,
28 because they all need to be taught about $SYSROOT, and
29 behave differently depending on whether they're called
30 at image build time, or on the target, as otherwise they
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/vsftpd/files/ |
| H A D | vsftpd.conf | 36 # Activate directory messages - messages given to remote users when they
113 # setting to NO, then users will be denied login unless they are explicitly
119 # userlist_file. If a user tries to log in using a name in this file, they
120 # will be denied before they are asked for a password. This may be useful in
133 # are not vsftpd specific. They apply to all FTP daemons which offer to put
|
| /openbmc/u-boot/doc/ |
| H A D | README.ARM-memory-map | 10 >How are they (should they be) set in your memory map above?
|
| /openbmc/qemu/tests/tcg/minilib/ |
| H A D | Makefile.target | 4 # The system tests are very constrained in terms of the library they
8 # They assume each arch has provided a putc function.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | index.rst | 17 components they use contain all the required security fixes, if and when they
|
| /openbmc/docs/architecture/code-update/ |
| H A D | firmware-update-over-redfish.md | 85 required before these requirements are implemented. They are here to ensure
200 administration authority to request this update so it is assumed they know what
201 they are doing and the level of security available with TFTP.
210 When new images are uploaded, they by default have no priority. When they are
211 activated, they are given the highest priority and all other images have their
223 stay at the forefront of these DMTF changes and ensure they are implemented as
224 they are released.
|
| /openbmc/qemu/tests/tcg/x86_64/system/ |
| H A D | validate-patch.py | 19 verify they match up and report if they do not.
|
| /openbmc/docs/ |
| H A D | anti-patterns.md | 198 Executables of type 2 should be placed in `/usr/bin` because they are intended
216 /usr/libexec Directory contains binaries for internal use only and they are
267 conditions it can recover from. Sometimes they try too hard and continue when it
270 Programmers also want to log what is happening in the application, so they write
272 for their use. They don't consider how the log entry is consumed by the BMC
309 REST API. They can respond to feedback about invalid input, or a need to
349 of writing debug data. They use std::cout, printf, fprintf, ... Doing this
357 on how to do it so everyone came up with whatever they were familiar with.
367 certain cases then they can protect these journald debug calls around a
422 In addition, because they are declared in a function scope, they are difficult
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | README.md | 76 `chassis0` and `host0` are special. If they exist, they are guaranteed to talk
80 entities as if they are one (if at all possible).
87 in mind as they likely desired to hard power off the system. In such a
110 a cold reboot then they should simply issue a power off transition request to
|