Go to file
Trevor Woerner 88f2064ca2 wic: add GPT partition names to partitions
A filesystem label (/dev/disk/by-label) is a property of, and stored in, the
filesystem itself. Partitions that are not destined to hold filesystems are
not formatted, therefore it is not possible to assign filesystem labels to
such partitions.

However, if GPT partitioning is being used, GPT supports the notion of
assigning labels/names to the partitions which are stored as part of the GPT
partition table itself (instead of being stored in the filesystem in the
partition). The naming is a bit confusing (different tools use different
names) but `wic` calls this "--part-name", `lsblk` calls this "PARTLABEL", and
`parted` calls this "name".

In Linux user-space these partition labels are referenced via
/dev/disk/by-partlabel and provide an excellent way of finding these GPT
partitions regardless of which backing device is actually being used (e.g.
mmcblk0, mmcblk1... i.e. emmc, sdcard...).

An example where this would be handy is for interacting with a stored U-Boot
environment. Another potential use would be to use one of the unused raw
partitions to store information such as MAC addresses, serial numbers, etc.
which could be set/updated "at the factory" as images are flashed.

Tested with both systemd and sysvinit on both rock-pi-e and rock-pi-s.

Reviewed-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
2024-04-22 09:16:55 -04:00
classes KERNEL_DEVICETREE: 32-bit re-org 2024-01-24 20:57:59 -05:00
conf rock-5[ab]: use regular yocto kernel 2024-03-07 17:05:07 -05:00
dynamic-layers/qt5-layer/recipes-qt/qt5 switch to the new bitbake OVERRIDE syntax 2021-08-04 21:59:14 -04:00
recipes-bsp u-boot: remove now-upstreamed rock-pi-e patches 2024-04-17 10:30:16 -04:00
recipes-graphics/mesa mesa: Enable Panfrost for PX30 2023-06-09 12:40:34 -04:00
recipes-kernel/linux rock-5[ab]: use regular yocto kernel 2024-03-07 17:05:07 -05:00
wic wic: add GPT partition names to partitions 2024-04-22 09:16:55 -04:00
COPYING.MIT Initial commit 2014-04-04 16:25:45 +02:00
README README: update submission information 2024-03-28 11:03:31 -04:00

OpenEmbedded BSP layer for Rockchip boards

About:

The purpose of this layer is to provide OpenEmbedded BSP support for
Rockchip-based devices using upstream sources as much as possible.

Dependencies:

URI: git://git.openembedded.org/openembedded-core
layers: meta
branch: matched branches (e.g. master, sumo, ...)

URI: git://git.yoctoproject.org/meta-arm
layers: meta-arm, meta-arm-toolchain
branch: matched branches (e.g. master, sumo, ...)

Status of supported boards:

builds and boots wic image:
	nanopi-m4
	nanopi-m4-2gb
	rock-pi-e
	rock-pi-4a
	rock-pi-4b
	rock-pi-4c
	rock64
	tinker-board
	tinker-board-s
	vyasa-rk3288
	firefly-rk3288
	nanopi-r4s
	rock-5b
	nanopi-r2s
	nanopi-m4b
	rock-pi-s
	rock-5a
	roc-rk3328-cc
	roc-rk3308-cc
	orangepi-5-plus
	rock-3a
	rock-4c-plus
builds:
	marsboard-rk3066
	radxarock
	rock2-square

Notes:

The latest ddr initializer for the rk3308 platform does not output
diagnostic messages to uart0. This causes a bunch of gibberish to
be printed to the console window which only becomes legible once
the linux kernel starts. I.e. the console output of the ddr
initialization routine, as well as u-boot is lost. An older
version of this same binary blob does, however, support output to
uart0 (making its diagnostic messages as well as u-boot available
on the console). By default the build assumes the user would like
to see these message and be able to have the option to interact
with u-boot.

IOW: for rk3308-based devices, an older version of rkbin is used.

If, however, the user would prefer to use the latest binary ddr
initializer from rkbin, simply set:

	RKBIN_RK3308_LATEST = "1"

in the configuration (e.g. conf/local.conf).

Maintenance:

Please send pull requests, patches, comments, or questions to the
yocto-patches mailing list (yocto-patches@lists.yoctoproject.org)
CCing the maintainer

When sending patches, please make sure the email subject line includes
"[meta-rockchip][PATCH]" and follow the community's patch submission
guidelines, as described in:
	https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
	https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

This can be configured within the repository with the following commands:

	git config sendemail.to yocto-patches@lists.yoctoproject.org
	git config sendemail.cc <your full email address>
	git config format.subjectprefix "meta-rockchip] [PATCH"

Then, to send your most recent commit (i.e. just one patch),
please use something like:

	git format-patch -M -1
	git send-email <your patch file>

Maintainer:

Trevor Woerner <twoerner@gmail.com>

Brief History:

2014 April
	- originally started by Julien Chauveau
	- Romain Perier joins
2014 Sep
	- Julien leaves
2015 Aug
	- Trevor Woerner joins
2017 Mar
	- developers from Rockchip fork this layer see:
		https://github.com/rockchip-linux/meta-rockchip.git
		http://rockchip.wikidot.com/yocto-user-guide
2017 May
	- Romain leaves
2018 Feb
	- Rockchip developers abandon their fork for buildroot
		http://opensource.rock-chips.com/wiki_Buildroot