public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: edk2-devel-01 <edk2-devel@lists.01.org>,
	Laszlo Ersek <lersek@redhat.com>
Cc: Shannon Zhao <zhaoshenglong@huawei.com>,
	Sakar Arora <sakar.arora@nxp.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 0/4] ArmVirtPkg: FdtClientDxe & HighMemDxe updates
Date: Thu, 15 Sep 2016 14:34:44 +0100	[thread overview]
Message-ID: <CAKv+Gu9xMEJ6zZpw1xkas7bW4JiY1RFujCRtD+87Ku5dE9rJDQ@mail.gmail.com> (raw)
In-Reply-To: <1473946233-10547-1-git-send-email-ard.biesheuvel@linaro.org>

On 15 September 2016 at 14:30, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> Patch #4 moves HighMemDxe to the FDT client protocol, and updates it to
> handle #address-cells/#size-cells values of <1> as well as <2>, and lets
> it deal with memory nodes whose 'reg' properties describe multiple disjoint
> regions.
>
> Patches #1 to #3 are somewhat preparatory in nature:
> - Patch #1 is a small thinko fix
> - Patch #2 drops the 'regelemsize' output parameter for 'reg' related methods
>   of the FDT client protocol in favour of addresscells/sizecells.
> - Patch #3 adds methods to iterate over all 'reg' properties of all memory nodes
>

Branch here
https://git.linaro.org/people/ard.biesheuvel/uefi-next.git/shortlog/refs/heads/virt-highmem-fdt

> Ard Biesheuvel (4):
>   ArmVirtPkg/FdtClientDxe: fix check for size of "reg" properties
>   ArmVirtPkg/FdtClientDxe: report address and size cell count directly
>   ArmVirtPkg/FdtClient: add methods to iterate over memory nodes
>   ArmVirtPkg/HighMemDxe: move to FDT client protocol
>
>  ArmVirtPkg/FdtClientDxe/FdtClientDxe.c                   |  84 +++++++++++++-
>  ArmVirtPkg/HighMemDxe/HighMemDxe.c                       | 120 +++++++++-----------
>  ArmVirtPkg/HighMemDxe/HighMemDxe.inf                     |  16 ++-
>  ArmVirtPkg/Include/Protocol/FdtClient.h                  |  29 ++++-
>  ArmVirtPkg/Library/ArmVirtGicArchLib/ArmVirtGicArchLib.c |   9 +-
>  ArmVirtPkg/Library/QemuFwCfgLib/QemuFwCfgLib.c           |   9 +-
>  ArmVirtPkg/XenAcpiPlatformDxe/XenAcpiPlatformDxe.c       |   8 +-
>  ArmVirtPkg/XenioFdtDxe/XenioFdtDxe.c                     |  10 +-
>  8 files changed, 196 insertions(+), 89 deletions(-)
>
> --
> 2.7.4
>


  parent reply	other threads:[~2016-09-15 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 13:30 [PATCH 0/4] ArmVirtPkg: FdtClientDxe & HighMemDxe updates Ard Biesheuvel
2016-09-15 13:30 ` [PATCH 1/4] ArmVirtPkg/FdtClientDxe: fix check for size of "reg" properties Ard Biesheuvel
2016-09-15 13:38   ` Laszlo Ersek
2016-09-15 13:40     ` Ard Biesheuvel
2016-09-15 13:30 ` [PATCH 2/4] ArmVirtPkg/FdtClientDxe: report address and size cell count directly Ard Biesheuvel
2016-09-15 13:42   ` Laszlo Ersek
2016-09-15 13:30 ` [PATCH 3/4] ArmVirtPkg/FdtClient: add methods to iterate over memory nodes Ard Biesheuvel
2016-09-15 13:57   ` Laszlo Ersek
2016-09-15 14:04     ` Ard Biesheuvel
2016-09-15 13:30 ` [PATCH 4/4] ArmVirtPkg/HighMemDxe: move to FDT client protocol Ard Biesheuvel
2016-09-15 14:15   ` Laszlo Ersek
2016-09-15 14:18     ` Ard Biesheuvel
2016-09-15 13:34 ` Ard Biesheuvel [this message]
2016-09-15 14:40   ` [PATCH 0/4] ArmVirtPkg: FdtClientDxe & HighMemDxe updates Ard Biesheuvel

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-list 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=CAKv+Gu9xMEJ6zZpw1xkas7bW4JiY1RFujCRtD+87Ku5dE9rJDQ@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox