Go to file
Pali Rohár 4c95e17903 libfdisk: (gpt) Add UUID for Marvell Armada 3700 Boot partition
This GPT UUID is used by BootROM on Marvell Armada 3700 SoC. BootROM
searches for GPT partition with this UUID on attached SATA disk and loads
bootloader from it.

Marvell Armada 3700 SoC is used e.g. on popular EspressoBIN SBC board which
has relatively solid Linux support.

Information about SATA booting and this GPT partition is currently
documented only in development version of ARM Trusted-Firmware-A


It is missing in official documentation for Armada 3720 BootROM and
therefore hard to find it.

Signed-off-by: Pali Rohár <pali.rohar@gmail.com>
2022-04-30 12:50:46 +02:00
.github/workflows ci: add a GHAction sending data to Coverity 2021-11-03 11:13:37 +00:00
Documentation docs: update v2.38-ReleaseNotes 2022-03-28 13:32:47 +02:00
bash-completion irqtop: support -C/--cpu-list 2022-04-01 10:21:31 +02:00
config build-sys: gtkdoc-fixxref v1.27 requires module option 2018-02-01 13:23:40 +01:00
disk-utils partx: remove memory leak to make scanners happy [coverity scan] 2022-03-17 11:22:29 +01:00
include libfdisk: (gpt) Add UUID for Marvell Armada 3700 Boot partition 2022-04-30 12:50:46 +02:00
lib lib/strutils: make sure ul_strtoXX functions always set errno 2022-04-21 11:57:56 +02:00
libblkid libblkid: fix FSSIZE docs 2022-04-26 10:32:05 +02:00
libfdisk meson: fix static builds creating conflicting targets 2022-04-14 10:28:29 -04:00
libmount libmount: cleanup UID and GIR parsing, add tests 2022-04-21 11:57:56 +02:00
libsmartcols meson: fix typoed copy-paste error that override other dependencies to blkid 2022-04-14 19:47:56 -04:00
libuuid libuuid: improve cache handling 2022-04-29 13:10:14 +02:00
login-utils libmount: fix typos 2022-04-01 10:21:41 +02:00
m4 build-sys: use $LIBS rather than LDFLAGS 2021-06-18 17:21:13 +02:00
man-common colors.adoc: format command name bold 2022-02-12 21:47:39 +01:00
misc-utils blkid: add FSSIZE tag with tests for XFS 2022-04-26 10:26:03 +02:00
po po: merge changes 2022-03-28 13:25:09 +02:00
po-man po-man: merge changes 2022-03-28 13:26:39 +02:00
schedutils man pages: unify output of --help and --version 2022-02-01 20:49:24 +01:00
sys-utils lsirq: improve --sort IRQ 2022-04-29 10:11:49 +02:00
term-utils meson: update for logindefs move 2022-03-30 11:14:31 +02:00
tests blkid: add FSSIZE tag with tests for XFS 2022-04-26 10:26:03 +02:00
text-utils column: fix memory use [coverity scan] 2022-03-31 09:55:23 +02:00
tools tools: add git-tp-sync-man 2022-03-07 14:21:44 +01:00
.editorconfig add .editorconfig 2016-01-25 00:12:14 +01:00
.gitignore build-sys: add blkpr to gitignore 2022-04-19 11:52:20 +02:00
AUTHORS docs: update AUTHORS file 2022-03-28 13:31:22 +02:00
COPYING docs: corrections to FSF license files, and postal address 2012-02-24 14:13:35 +01:00
ChangeLog docs: Correct ChangeLog URL to history log. 2020-05-11 09:48:43 +02:00
Makefile.am build-sys: distribute Meson files 2022-03-01 11:22:33 +01:00
NEWS build-sys: release++ (v2.38) 2022-03-28 13:33:44 +02:00
README docs: update IRC address 2021-11-08 13:09:06 +01:00
README.licensing docs: add GPLv3 text 2019-11-08 11:10:54 +01:00
autogen.sh build-sys: use set +e before patch --try in ./autogen.sh 2021-10-21 18:27:46 +02:00
configure.ac blkpr: add block persistent reservations command 2022-04-06 11:04:13 +02:00
meson.build meson: pass the correct absolute path to config.h 2022-04-14 10:55:29 -04:00
meson_options.txt meson: make raw(7) optional 2021-09-23 14:09:35 +02:00
util-linux.doap docs: update github URL 2021-11-03 13:58:21 +01:00



		util-linux is a random collection of Linux utilities

     Note: for the years 2006-2010 this project was named "util-linux-ng".


      See Documentation/howto-compilation.txt.


      E-MAIL:  util-linux@vger.kernel.org
      URL:     http://vger.kernel.org/vger-lists.html#util-linux
      ARCHIVE: https://lore.kernel.org/util-linux/

      The mailing list will reject email messages that contain:
       - more than 100K characters
       - html
       - spam phrases/keywords
      See: http://vger.kernel.org/majordomo-info.html#taboo


      #util-linux at libera.chat:


      The IRC channel and Mailing list are for developers and project
      maintainers. For end users it is recommended to utilize the
      distribution's support system.


      E-MAIL: util-linux@vger.kernel.org
      Web:    https://github.com/util-linux/util-linux/issues

      Bug reports with sensitive or private information: Karel Zak <kzak@redhat.com>

      This project has no resources to provide support for distribution specific
      issues. For end users it is recommended to utilize the distribution's
      support system.


      PO files are maintained by:


      Standard releases:
	     major = fatal and deep changes
	     minor = typical release with new features
	     maint = maintenance releases; bug fixes only

      Development releases:


 Download archive:

 See also:

 SCM (Source Code Management) Repository:

    Primary repository:
	  git clone git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git

    Backup repository:
	  git clone git://github.com/util-linux/util-linux.git

    Web interfaces:

      Note: the GitHub repository may contain temporary development branches too.

      The kernel.org repository contains master (current development) and stable/*
      (maintenance) branches only. All master or stable/* changes are always pushed
      to both repositories at the same time.

    Repository Branches: 'git branch -a'
	  master branch
	   - current development
	   - the source for stable releases when deemed ready.
	   - day-to-day status is: 'it works for me'. This means that its
	     normal state is useful but not well tested.
	   - long-term development or invasive changes in active development are
	     forked into separate 'topic' branches from the tip of 'master'.

	  stable/ branches
	   - public releases
	   - branch name: stable/v<major>.<minor>.
	   - created from the 'master' branch after two or more release
	     candidates and the final public release. This means that the stable
	     releases are committed, tagged, and reachable in 'master'.
	   - these branches then become forked development branches. This means
	     that any changes made to them diverge from the 'master' branch.
	   - maintenance releases are part of, and belong to, their respective
	     stable branch. As such, they are tags(<major>.<minor>.<maint>) and
	     not branches of their own. They are not part of, visible in, or
	     have anything to do with the 'master' development branch. In git
	     terminology: maintenance releases are not reachable from 'master'.
	   - when initially cloned (as with the 'git clone' command given above)
	     these branches are created as 'remote tracking branches' and are
	     only visible by using the -a or -r options to 'git branch'. To
	     create a local branch use the desired tag with this command:
	     'git checkout -b v2.29.2 v2.29.2'

    Tags: 'git tag'
	   - a new tag object is created for every release.
	   - tag name: v<version>.
	   - all tags are signed by the maintainer's PGP key.

    Known Bugs:
	- don't use tag v2.13.1 (created and published by mistake),
	  use v2.13.1-REAL instead.


 1) development (branch: <master>)

 2) master release (tags: v2.29-rc1, v2.29-rc2, v2.29, branch: <master>)

 3) development (work on v2.30, branch: <master>)

 4) fork -- create a new branch <stable/v2.29> based on tag v2.29

     4a) new patches or cherry-pick patches from <master> (branch: <stable/v2.29>)

     4b) stable release (tag: v2.29.1, branch: <stable/v2.29>)

     4c) more patches; another release (tag: v2.29.2, branch: <stable/v2.29>)

 5) master release v2.30 (branch: <master>)

where 3) and 4) happen simultaneously.