Template:ARMSoC: Difference between revisions

Latest revision as of 15:54, 3 February 2022

Template documentation [edit]

This documentation is transcluded from Template:ARMSoC/doc. It will not be transcluded on pages that use this template.

This template provides a formatted page displaying information about a particular SoC in a consistent format. A common use for this template is on the Architecture/ARM pages.

Syntax

Copy this into your article and leave those sections blank that you don't need!

{{ARMSoC
 | name=
 | image=
 | caption=
 | manufacturer=
 | architecture=
 | cpu=
 | gpu=
 | memory=
 | vpu=
 | audio=
 | network=
 | storage=
 | usb=
 | other=
 | supported_release=
 | soc_website=
 | brief_overview=
 | kernel_status=
 | bootloader_status=
 | other_details=
}}

Parameters

The following parameters are recognized. Parameters in CAPITAL letters are required.

name: The name of the SoC. This overrides the subpage name.
image: Upload your picture by clicking "Upload file" on the left pane. Then put the filename here. For example, hikey-620.png
caption: Caption text underneath the image
manufacturer: The SoC manufacturer
architecture: The CPU architecture
cpu: CPU details
gpu: Details of the graphical processing unit
memory: Details about the onboard memory
vpu: Details about video offload
audio: Details about audio
network: Details about network ports, wireless radios, etc.
storage: Details about onboard storage
usb: Details of USB ports
other: Other details
supported_release: The list of supported Fedora releases for this SoC
soc_website: The URL to the upstream website for this SoC
brief_overview: A brief overview of the SoC
kernel_status: The status of kernel support for the features of this SoC
bootloader_status: The status of the bootloader and firmware for this SoC
other_details: Other details about this SoC that might be useful to know

Example

Many examples of this template can be found at Special:WhatLinksHere.

@@ Line 23: / Line 23: @@
 == {{{name|{{SUBPAGENAME}}}}} ==
-Based on NXP’s Layerscape LX2160A’s 16 Arm Cortex A72 CPU, with SODIMM Slots, SATA, USB3, PCIe and onboard 10/25/100G networking.
+{{{brief_overview|Brief overview of SoC goes here...}}}
 == Kernel features status and overview ==
+{{{kernel_status|Brief overview of the kernel status}}}
 == Bootloader/firmware status and overview ==
-The system should be provisioned with a recent UEFI firmware image from https://images.solid-run.com/LX2k/lx2160a_uefi
+{{{bootloader_status|Brief overview of bootloader or firmware notes go here...}}}
-Choose the correct firmware based on whether it will be flashed to the SPI or SD and matches the installed RAM speed.
-The solidrun pages have details on how to assure the correct firmware is installed, but for SD the process is approximatly:
-* Download the image
-* decompress it with xzdec,
-* dd it to a raw sd card like: dd if=lx2160acex7_2200_700_2400_8_5_2.img of=/dev/sdX where sdX is the SD card.
-* Plug the SD card into the board.
-* Make sure firmware boot source switches are set off-ON-ON-ON-ON-off.
 == Other details ==
-* On the first boot of the installer, it may be required to add `arm-smmu.disable_bypass=0` to the grub/kernel command line. That will then propagate to the installed system and remain over upgrades.
+{{{other_details| Anything else to highlight}}}
-* To manage the SFP+ ports please install the "restool" package.
-* To auto-enable the SFP+ ports, it may be necessary to add a udev rule to /etc/udev/rules.d. For example, a file named fsl_mc_bus.rules containing: `ACTION=="add", SUBSYSTEM=="fsl-mc", ENV{DEVTYPE}=="fsl_mc_bus_dpmac", RUN+="/usr/bin/flock /usr/bin/ls-addni -c '(PATH=/usr/bin /usr/bin/ls-addni %k)'`
 [[Category:AArch64]]

Search