| /openbmc/u-boot/drivers/power/ |
| H A D | Kconfig | 20 Select this for boards which do not use a PMIC.
29 A10s boards.
38 A10, A13 and A20 boards.
47 A23 and A31 boards.
55 Say y here to enable support for the axp809 pmic found on A80 boards.
71 H3 boards.
82 disable dcdc1. On A23 / A31 / A33 (axp221) boards dcdc1 is used for
84 sdcard interfaces, etc. On most boards dcdc1 is undervolted to 3.0V to
100 On A10(s) / A13 / A20 boards dcdc2 is VDD-CPU and should be 1.4V.
101 On A31 boards dcdc2 is used for VDD-GPU and should be 1.2V.
[all …]
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | board.py | 7 """A single regular expression for matching boards to build"""
99 class Boards: class
100 """Manage a list of boards."""
116 """Read a list of boards from a board file.
121 fname: Filename of boards.cfg file
143 """Return a list of available boards.
151 """Build a dictionary containing all the boards.
164 """Return a dictionary containing the selected boards
176 """Return a list of selected boards
184 """Return a list of selected boards
[all …]
|
| H A D | control.py | 37 str = '%s %s for %d boards' % (
51 provided by the user, and the value is the list of boards
53 in 400 boards, so in this case the key would be 'arm' and
55 boards_selected: Dict of selected boards, key is target name,
79 print arg, ': %d boards' % len(why_selected[arg])
82 print ('Total boards to build for each commit: %d\n' %
110 def DoBuildman(options, args, toolchains=None, make_func=None, boards=None, argument
123 board: Boards() object to use, containing a list of available
124 boards. If this is None it will be created and scanned.
202 # Work out what subset of the boards we are building
[all …]
|
| H A D | bsettings.py | 91 # Special flags to pass to 'make' for certain boards, e.g. to pass a test
92 # flag and build tag to snapper boards:
93 # snapper-boards=ENABLE_AT91_TEST=1
94 # snapper9260=${snapper-boards} BUILD_TAG=442
95 # snapper9g45=${snapper-boards} BUILD_TAG=443
|
| H A D | README | 25 which boards fail on which commits, and which errors come up. It aims
66 Buildman produces a concise summary of which boards succeeded and failed.
108 source has changed, and will build all specified boards in this case.
110 Buildman is optimised for building many commits at once, for many boards.
113 a few commits or boards, it will be pretty slow. As a tip, if you don't
118 Selecting which boards to build
121 Buildman lets you build all boards, or a subset. Specify the subset by passing
123 SOC name, or anything else in the boards.cfg file. Multiple arguments are
127 * 'tegra20' All boards with a Tegra20 SoC
128 * 'tegra' All boards with any Tegra Soc (Tegra20, Tegra30, Tegra114...)
[all …]
|
| H A D | test.py | 90 boards = [ variable
124 # Set up boards to build
125 self.boards = board.Boards()
126 for brd in boards:
127 self.boards.AddBoard(board.Board(*brd))
128 self.boards.SelectBoards([])
171 def assertSummary(self, text, arch, plus, boards, outcome=OUTCOME_ERR): argument
179 for board in boards:
196 board_selected = self.boards.GetSelectedDict()
198 # Build the boards for the pre-defined commits and warnings/errors
[all …]
|
| H A D | func_test.py | 36 boards = [ variable
187 self._boards = board.Boards()
188 for brd in boards:
194 self._total_builds = self._commits * len(boards)
223 make_func=self._HandleMake, boards=self._boards,
416 """Test that buildman aborts when there are no boards"""
417 self._boards = board.Boards()
426 self.assertIn('Building current source for %d boards' % len(boards),
441 self.assertIn('Building %d commits for %d boards' %
442 (self._commits, len(boards)), lines[0].text)
[all …]
|
| H A D | builder.py | 35 commits for different boards on multiple CPUs at once.
45 commit and then built it for all boards. Using separate directories for each
69 As an example, say we are building branch 'us-net' for boards 'sandbox' and
180 _base_board_dict: Last-summarised Dict of boards
187 _show_unknown: Show unknown boards (those not built) in summary
240 show_unknown: Show unknown boards (those not built) in summary
335 list_error_boards: Show the boards which caused each error/warning
458 # When building all boards for a commit, we can print a commit
738 board_selected: Dict containing boards to summarise
746 Dict containing boards which passed building this commit.
[all …]
|
| /openbmc/entity-manager/test/ |
| H A D | test_topology.cpp | 56 BoardMap boards; in TEST() local
58 auto assocs = topo.getAssocs(std::views::keys(boards)); in TEST()
66 BoardMap boards{{subchassisPath, "BoardA"}, {superchassisPath, "BoardB"}}; in TEST() local
71 auto assocs = topo.getAssocs(std::views::keys(boards)); in TEST()
86 BoardMap boards{{subchassisPath, "BoardA"}, {superchassisPath, "BoardB"}}; in TEST() local
93 auto assocs = topo.getAssocs(std::views::keys(boards)); in TEST()
101 BoardMap boards{{subchassisPath, "BoardA"}, {superchassisPath, "BoardB"}}; in TEST() local
106 auto assocs = topo.getAssocs(std::views::keys(boards)); in TEST()
114 BoardMap boards{{subchassisPath, "BoardA"}, {superchassisPath, "BoardB"}}; in TEST() local
120 auto assocs = topo.getAssocs(std::views::keys(boards)); in TEST()
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | layer-contents.md | 27 For usecases where compatibility of more boards is required, the layer provides
28 machines that are tagetting a wider support of Raspberry Pi boards.
32 This machine targets support for all the ARMv7-based Raspberry Pi boards. It
34 all the relevant boards.
38 This machine targets support for all the ARMv8-based Raspberry Pi boards. It
40 all the relevant boards.
53 Be aware that the WiFi and Bluetooth firmware for the supported boards
|
| /openbmc/u-boot/doc/ |
| H A D | README.kconfig | 47 You can simply remove the prefixes. Do not add them for new boards.
76 - include/configs/<board>.h (exists for all boards)
88 Conversion from boards.cfg to Kconfig
91 Prior to Kconfig, boards.cfg was a primary database that contained Arch, CPU,
92 SoC, etc. of all the supported boards. It was deleted when switching to
93 Kconfig. Each field of boards.cfg was converted as follows:
106 Tips to add/remove boards
132 [2] Remove include/configs/<target>.h if it is not used by any other boards
134 by any other boards
143 - The option field of boards.cfg, which was used for the pre-Kconfig
[all …]
|
| H A D | README.AMCC-eval-boards-cleanup | 2 Cleanup of AMCC eval boards (Walnut/Sycamore, Bubinga, Ebony, Ocotea)
5 Changes to all AMCC eval boards:
9 boards.
21 Sycamore/Walnut (one port supporting both eval boards):
24 o Cleanup to allow easier "cloning" for different (custom) boards:
|
| H A D | README.zynq | 10 like supported boards, ML status and TODO list.
12 2. Zynq boards
58 - Added zynq boards named - zc70x, zed, microzed, zc770_xm010/xm011/xm012/xm013
68 - Added basic FDT support for zynq boards
75 [1] http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC702-G.htm
76 [2] http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC706-G.htm
|
| /openbmc/qemu/docs/devel/ |
| H A D | kconfig.rst | 8 targets, where each target can emulate various boards and at the same
11 card, even though the boards use different PCI host bridges, and they
13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
16 Each QEMU target enables a subset of the boards, devices and buses that
24 * new targets and boards can be added without knowing in detail the
25 architecture of the hardware emulation subsystems. Boards only have
31 of boards or devices. For example, by default most targets will include
198 some boards (notably s390) easily support a subset of PCI devices,
208 **boards**
229 Boards specify their constituent devices using ``imply`` and ``select``
[all …]
|
| /openbmc/u-boot/arch/mips/mach-bmips/ |
| H A D | Kconfig | 145 Comtrend AR-5315u boards have a BCM6318 SoC with 64 MB of RAM and 16
156 Comtrend AR-5387un boards have a BCM6328 SoC with 64 MB of RAM and 16
167 Comtrend CT-5361 boards have a BCM6348 SoC with 16 MB of RAM and 4 MB
178 Comtrend VR-3032u boards have a BCM63268 SoC with 64 MB of RAM and
189 Comtrend WAP-5813n boards have a BCM6369 SoC with 64 MB of RAM and
200 Huawei EchoLife HG556a boards have a BCM6358 SoC with 64 MB of RAM
211 Netgear CG3100D boards have a BCM3380 SoC with 64 MB of RAM and 8 MB
222 Netgear DGND3700v2 boards have a BCM6362 SoC with 64 MB of RAM and
233 Sagem F@ST1704 boards have a BCM6338 SoC with 16 MB of RAM and 4 MB
244 SFR NeufBox 4 (Sercomm) boards have a BCM6358 SoC with 32 MB of RAM
|
| /openbmc/u-boot/arch/arm/mach-snapdragon/ |
| H A D | Kconfig | 16 bool "96Boards Dragonboard 410C"
19 Support for 96Boards Dragonboard 410C. This board complies with
30 bool "96Boards Dragonboard 820C"
32 Support for 96Boards Dragonboard 820C. This board complies with
|
| /openbmc/u-boot/board/freescale/p1_p2_rdb_pc/ |
| H A D | README | 3 P1_P2_RDB_PC represents a set of boards including
16 Key features on these boards include:
25 As these boards use soldered DDR chips not regular DIMMs, an on-board EEPROM
29 this approach. ODT option is forced to fit this set of boards, again because
40 Some boards have QE module in the silicon (P1021 and P1025). QE and eLBC have
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 21 possible daughter boards that can be attached to this mother board. Different
22 daughter boards then either offer the slightly different functionality, or the
29 system, depending on which daughter boards are connected to the motherboard.
35 boards is then detected, and the corresponding device tree overlays are applied
36 to support the components on the daughter boards.
39 provide a way to find out if and which daughter boards are installed for this
43 integrated, and is used on some boards to alter the device tree that is later
68 boards have to implement the function board_fix_fdt, which has the following
120 not, since they are on daughter boards) on a I2C bus are queried for, and
|
| /openbmc/u-boot/board/congatec/cgtqmx6eval/ |
| H A D | README | 1 U-Boot for the Congatec QMX6 boards
4 QMX6 boards.
9 - Build U-Boot for Congatec QMX6 boards:
59 The boot medium of Congatec QMX6 boards is the SPI NOR flash, so boot
|
| /openbmc/qemu/configs/devices/ppc64-softmmu/ |
| H A D | default.mak | 3 # Include all 32-bit boards
6 # Boards are selected by default, uncomment to keep out of the build.
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap3/ |
| H A D | Kconfig | 52 bool "CompuLab CM-T3530 and CM-T3730 boards"
58 bool "CompuLab CM-T3517 boards"
184 The default memory controller on most OMAP3 boards is SDRC.
189 Enable this on boards like AM3517 which use EMIF4 controller
|
| /openbmc/u-boot/board/hisilicon/hikey/ |
| H A D | README | 4 HiKey is the first certified 96Boards Consumer Edition board. The board/SoC has: -
13 https://github.com/96boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/HiKey_s…
16 https://github.com/96boards/documentation/blob/master/consumer/hikey/hikey620/hardware-docs/Hi6220V…
34 > git clone https://github.com/96boards-hikey/edk2 -b testing/hikey960_v2.5
36 > git clone https://github.com/96boards-hikey/l-loader -b testing/hikey960_v1.2
37 > git clone https://github.com/96boards-hikey/OpenPlatformPkg -b testing/hikey960_v1.3.4
38 > git clone https://github.com/96boards-hikey/atf-fastboot
39 …> wget https://snapshots.linaro.org/96boards/reference-platform/components/uefi-staging/latest/hik…
47 …> wget -P ~/hikey/bin https://snapshots.linaro.org/96boards/reference-platform/components/uefi-sta…
|
| /openbmc/u-boot/board/boundary/nitrogen6x/ |
| H A D | README | 2 Freescale i.MX6Q SabreLite boards
6 Freescale i.MX6Q SabreLite boards.
24 The default bootcmd for these boards is configured
73 board configurations is shown in the boards.cfg file:
|
| /openbmc/u-boot/arch/arm/mach-owl/ |
| H A D | Kconfig | 11 bool "96Boards Bubblegum-96"
13 Support for 96Boards Bubblegum-96. This board complies with
|
| /openbmc/openbmc/meta-evb/ |
| H A D | README.md | 4 This is the OpenBMC Evaluation Board (EVB) layer. The boards in the EVB layer
9 be used instead. Boards might be found be in both the EVB layer and the BSP
|