public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ming Huang <ming.huang@linaro.org>
To: leif.lindholm@linaro.org, linaro-uefi@lists.linaro.org,
	edk2-devel@lists.01.org, graeme.gregory@linaro.org
Cc: ard.biesheuvel@linaro.org, guoheyi@huawei.com,
	wanghuiqiang@huawei.com, huangming23@huawei.com,
	zhangjinsong2@huawei.com, huangdaode@hisilicon.com,
	john.garry@huawei.com, Ming Huang <ming.huang@linaro.org>
Subject: [PATCH edk2-non-osi v1 1/1] Hisilicon/D0x: Fix invoke SetMemorySpaceAttributes error bug
Date: Wed,  4 Jul 2018 15:49:30 +0800	[thread overview]
Message-ID: <20180704074930.7329-2-ming.huang@linaro.org> (raw)
In-Reply-To: <20180704074930.7329-1-ming.huang@linaro.org>

The edk2 commit bacfd6e let CpuDxe running latter.
CpuDxe is needed by gDS->SetMemorySpaceAttributes, and
gDS->SetMemorySpaceAttributes is invoked by some drivers.

This issue can solve by adding Depex on gEfiCpuArchProtocolGuid
to SFCDriver.

Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ming Huang <ming.huang@linaro.org>
---
 Platform/Hisilicon/D05/Drivers/SFC/SFCDriver.depex | Bin 2 -> 36 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/Platform/Hisilicon/D05/Drivers/SFC/SFCDriver.depex b/Platform/Hisilicon/D05/Drivers/SFC/SFCDriver.depex
index 2a47cc2..e5c4b16 100644
Binary files a/Platform/Hisilicon/D05/Drivers/SFC/SFCDriver.depex and b/Platform/Hisilicon/D05/Drivers/SFC/SFCDriver.depex differ
-- 
2.17.0



  reply	other threads:[~2018-07-04  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  7:49 [PATCH edk2-non-osi v1 0/1] Fix invoke SetMemorySpaceAttributes error bug Ming Huang
2018-07-04  7:49 ` Ming Huang [this message]
2018-07-13  7:33 ` Ard Biesheuvel
2018-07-13  8:24   ` Ming
2018-07-25 11:13 ` Ard Biesheuvel
2018-08-15 14:17   ` Leif Lindholm

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=20180704074930.7329-2-ming.huang@linaro.org \
    --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