All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hoyes <peter.hoyes@arm.com>
To: u-boot@lists.denx.de
Cc: andre.przywara@arm.com, diego.sueiro@arm.com,
	Peter Hoyes <Peter.Hoyes@arm.com>
Subject: [PATCH v2 0/5] VExpress64 board family improvements
Date: Thu, 11 Nov 2021 09:25:58 +0000	[thread overview]
Message-ID: <20211111092603.774415-1-peter.hoyes@arm.com> (raw)

From: Peter Hoyes <Peter.Hoyes@arm.com>

These patches add the follow improvements to the VExpress64 board family
(BASE_FVP and Juno):

 * Add documentation
 * Allow use of OF_BOARD for BASE_FVP (off by default)
 * Allow use of the virtio-net driver (off by default)
 * Refactor header file to make it easier to add new FVPs with similar
 * memory layouts
 * Fix issue where fdt is called with invalid arguments during BASE_FVP
   boot
 * Update BASE_FVP env vars to recommended names

This is towards future work to add support for the
FVP_BaseR_AEMv8R.

Changes in v2:
 * Add note about building U-Boot with TF-A to FVP doc
 * Modify BASE_FVP env var addresses to allow space for larger kernels
 * OF_BOARD cleanups

Peter Hoyes (5):
  doc: Add documentation for the Arm VExpress64 board configs
  vexpress64: Refactor header file to make it easier to add new FVPs
  vexpress64: Clean up BASE_FVP boot configuration
  vexpress64: Enable OF_CONTROL and OF_BOARD for VExpress64
  vexpress64: Enable VIRTIO_NET network driver

 board/armltd/vexpress64/Kconfig               |   2 +-
 board/armltd/vexpress64/Makefile              |   2 +-
 board/armltd/vexpress64/lowlevel_init.S       |  12 +++
 board/armltd/vexpress64/vexpress64.c          |  33 ++++++
 doc/README.semihosting                        |   2 +-
 doc/board/armltd/index.rst                    |   9 ++
 doc/board/armltd/vexpress64.rst               |  51 +++++++++
 doc/board/index.rst                           |   1 +
 .../{vexpress_aemv8a.h => vexpress_aemv8.h}   | 102 ++++++++++--------
 9 files changed, 167 insertions(+), 47 deletions(-)
 create mode 100644 board/armltd/vexpress64/lowlevel_init.S
 create mode 100644 doc/board/armltd/index.rst
 create mode 100644 doc/board/armltd/vexpress64.rst
 rename include/configs/{vexpress_aemv8a.h => vexpress_aemv8.h} (72%)

-- 
2.25.1


             reply	other threads:[~2021-11-11  9:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  9:25 Peter Hoyes [this message]
2021-11-11  9:25 ` [PATCH v2 1/5] doc: Add documentation for the Arm VExpress64 board configs Peter Hoyes
2021-11-11 17:10   ` Andre Przywara
2022-01-07 17:03   ` Tom Rini
2021-11-11  9:26 ` [PATCH v2 2/5] vexpress64: Refactor header file to make it easier to add new FVPs Peter Hoyes
2021-11-11 17:10   ` Andre Przywara
2022-01-07 17:03   ` Tom Rini
2021-11-11  9:26 ` [PATCH v2 3/5] vexpress64: Clean up BASE_FVP boot configuration Peter Hoyes
2021-11-11 17:10   ` Andre Przywara
2022-01-07 17:04   ` Tom Rini
2021-11-11  9:26 ` [PATCH v2 4/5] vexpress64: Enable OF_CONTROL and OF_BOARD for VExpress64 Peter Hoyes
2021-11-11 17:10   ` Andre Przywara
2022-01-07 17:03   ` Tom Rini
2021-11-11  9:26 ` [PATCH v2 5/5] vexpress64: Enable VIRTIO_NET network driver Peter Hoyes
2021-11-11 17:11   ` Andre Przywara
2022-01-07 17:03   ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211111092603.774415-1-peter.hoyes@arm.com \
    --to=peter.hoyes@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=diego.sueiro@arm.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.