| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 14 now, as you are starting your own project, it isn't exactly straightforward what
64 #. **Create your own layer for the BSP you're going to use**.
67 BSP, :ref:`create your own layer for the BSP <bsp-guide/bsp:creating a new
75 #. **Write your own recipe to build additional software support that isn't
77 Creating your own recipe is especially important for custom application
87 that you have your own image recipe --- don't try appending to existing image
96 #. **Consider creating your own distribution**.
97 When you get to a certain level of customization, consider creating your own
102 your own distribution in a new layer inheriting from Poky but overriding what
105 local settings, it's time to :ref:`consider creating your own distribution
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | custom-distribution.rst | 3 Creating Your Own Distribution
16 your own distribution.
18 To create your own distribution, the basic steps consist of creating
19 your own distribution layer, creating your own distribution
25 separate. It is strongly recommended that you create and use your own
26 layer for configuration and code. Using your own layer as compared to
101 ":ref:`dev-manual/layers:creating your own layer`" and
|
| /openbmc/phosphor-ipmi-flash/ |
| H A D | bmc_json_config.md | 14 write your own. It's helpful to start here.
182 ## Writing your own json Configuration
184 If you wish to write your own json configuration, you simply create a legal json
191 default-provided configuration files, and also add your own to add additional
246 ### Installing your own json configuration
248 To install your own configuration(s) you can add your own bbappend file that
252 ## Adding your own handler type
270 ## Adding your own action type
|
| /openbmc/qemu/hw/misc/ |
| H A D | ivshmem-flat.c | 71 IvshmemFTState *s = container_of(own_peer, IvshmemFTState, own); in ivshmem_flat_irq_handler()
91 /* Own ID */ in ivshmem_flat_find_peer()
92 if (s->own.id == peer_id) { in ivshmem_flat_find_peer()
93 return &s->own; in ivshmem_flat_find_peer()
162 * If it's the device's own ID, register also the handler for the eventfd in ivshmem_flat_add_vector()
165 if (peer == &s->own) { in ivshmem_flat_add_vector()
236 ret = s->own.id; in ivshmem_flat_iomem_read()
349 * 1 OWN PEER ID -1 |-- Header/Greeting in ivshmem_flat_connect_server()
374 s->own.id = peer_id; in ivshmem_flat_connect_server()
375 s->own.vector_counter = 0; in ivshmem_flat_connect_server()
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | python-ldap | 6 responsible for their own choice and use of this software for their
7 own purposes. By using this software, each user agrees that the
|
| H A D | SAX-PD | 6 In fact, it`s not possible to own a license to SAX, since it`s been placed in the public domain.
22 …a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it…
|
| H A D | WXwindows | 38 under your own terms, binary object code versions of works based
49 4. If you write modifications of your own for this library, it is your
|
| H A D | LPL-1.0 | 15 …odules of software distributed in conjunction with the Program under their own license agreement, …
41 …se to distribute the Program in any form under this Agreement or under its own license agreement, …
44 …rce code or other tangible form, a copy of this Agreement or Distributor's own license agreement i…
45 3. if distributed under Distributor's own license agreement, such license agreement:
59 …ent negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
|
| H A D | swrule | 1 …ot liable for any problem that may or may not result from using this package. Use at your own risk.
|
| H A D | TPDL | 2 License hereby granted for anyone to use, modify or redistribute this module at their own risk. Ple…
|
| /openbmc/phosphor-fan-presence/ |
| H A D | dbus_paths.hpp | 6 // Control Application's D-Bus busname to own
13 // Thermal Application's D-Bus busname to own
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-3.3.rst | 133 - ``iproute2``: split ``ip`` binary to its own package
134 - ``net-tools``: split ``mii-tool`` into its own package
135 - ``procps``: split ``ps`` and ``sysctl`` into their own packages
139 - ``util-linux``: ``libuuid`` has been split out to its own
153 of course specify your own :term:`DISTRO_VERSION` value as desired
154 (particularly if you create your own custom distro configuration).
|
| H A D | migration-5.0.rst | 159 their own distribution and not use Poky. To encourage this behaviour
162 own distribution this message will not show up.
164 For information on how to create your own distribution, see
165 ":ref:`dev-manual/custom-distribution:creating your own distribution`".
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | faq.rst | 12 How do I use my own Linux kernel ``.config`` file?
26 How do I use my own Linux kernel sources?
30 ":ref:`kernel-dev/common:working with your own sources`"
|
| /openbmc/u-boot/lib/efi/ |
| H A D | Kconfig | 8 application, with U-Boot using EFI's drivers instead of its own.
33 Set the amount of EFI RAM which is claimed by U-Boot for its own
|
| H A D | efi.c | 22 * so it uses the wrong compiler flags. Add our own memset() here.
33 * Since the EFI stub cannot access most of the U-Boot code, add our own
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/tayga/files/ |
| H A D | tayga.conf | 4 # Modify this to use your own addresses!!
21 # requires its own address because it acts as an IPv4 and IPv6 router, and
33 # requires its own address because it acts as an IPv4 and IPv6 router, and
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | id_map.hpp | 133 * Map from device IDs to Device objects. Does not own the objects.
138 * Map from rail IDs to Rail objects. Does not own the objects.
143 * Map from rule IDs to Rule objects. Does not own the objects.
|
| /openbmc/openbmc/poky/meta/recipes-support/db/db/ |
| H A D | 0001-clock-Do-not-define-own-timespec.patch | 4 Subject: [PATCH] clock: Do not define own timespec
27 - * time.h include file patterns out there, it's easier to declare our own name
|
| /openbmc/qemu/stubs/ |
| H A D | is-daemonized.c | 3 /* Win32 has its own inline stub */
|
| /openbmc/openbmc/poky/meta-poky/recipes-core/base-files/files/poky/ |
| H A D | motd | 4 own distribution for production use.
|
| /openbmc/u-boot/net/ |
| H A D | net.c | 21 * Prerequisites: - own ethernet address
22 * We want: - own IP address
29 * Prerequisites: - own ethernet address
30 * We want: - own IP address
35 * Prerequisites: - own ethernet address
36 * We want: - own IP address
42 * Prerequisites: - own ethernet address
43 * - own IP address
50 * Prerequisites: - own ethernet address
57 * Prerequisites: - own ethernet address
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/conf/machine/include/ |
| H A D | rpi-default-settings.inc | 5 # RPI kernel has errors of its own which should be filtered
|
| /openbmc/qemu/tests/ |
| H A D | dbus-vmstate-daemon.sh | 34 <deny own="*"/>
65 <allow own="org.qemu.VMState1"/>
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/dbus/dbus-perms/ |
| H A D | org.openbmc.conf | 5 <allow own="*"/>
|