public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: devel@edk2.groups.io
Cc: leif@nuviainc.com, Samer.El-Haj-Mahmoud@arm.com,
	Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: [PATCH edk2-platforms 0/2] SynQuacer: fix driver model integration of NetSec
Date: Wed,  8 Apr 2020 18:11:36 +0200	[thread overview]
Message-ID: <20200408161138.18289-1-ard.biesheuvel@arm.com> (raw)

Currently, the way the SynQuacer NetSec driver implements the EFI driver
model is slightly quirky. Two changes are needed to move it closer to the
intent of the driver model, which is the ability to boot using only the
drivers that are required to drive the devices that are needed at boot.
This series does not complete the picture entirely yet for SynQuacer, and
it still relies on the unconditional EfiBootManagerConnectAll() call that
exists in the PlatformBootManagerLib implementation in ArmPkg. This is left
for future work.

Ard Biesheuvel (2):
  Silicon/SynQuacer/PlatformDxe: defer device registration until
    EndOfDxe
  Silicon/SynQuacer/NetsecDxe: move device path to root device

 .../Drivers/Net/NetsecDxe/NetsecDxe.c         | 12 ---
 .../Drivers/Net/NetsecDxe/NetsecDxe.h         |  9 --
 .../Drivers/PlatformDxe/PlatformDxe.c         | 92 +++++++++++++++++--
 .../Drivers/PlatformDxe/PlatformDxe.h         |  1 +
 .../Drivers/PlatformDxe/PlatformDxe.inf       |  3 +
 5 files changed, 86 insertions(+), 31 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-04-08 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 16:11 Ard Biesheuvel [this message]
2020-04-08 16:11 ` [PATCH edk2-platforms 1/2] Silicon/SynQuacer/PlatformDxe: defer device registration until EndOfDxe Ard Biesheuvel
2020-04-08 16:11 ` [PATCH edk2-platforms 2/2] Silicon/SynQuacer/NetsecDxe: move device path to root device Ard Biesheuvel
2020-04-08 16:26 ` [PATCH edk2-platforms 0/2] SynQuacer: fix driver model integration of NetSec Leif Lindholm
2020-04-09  5:48   ` 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=20200408161138.18289-1-ard.biesheuvel@arm.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