public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Borzeszkowski, Alan" <alan.borzeszkowski@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>, devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH 1/1] MdeModulePkg: Load Serial driver in early DXE
Date: Fri, 10 May 2024 08:03:34 -0700	[thread overview]
Message-ID: <32021.1715353414607689205@groups.io> (raw)
In-Reply-To: <MN6PR11MB8244060A85D19343D3C2D7038CE72@MN6PR11MB8244.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

Sorry, I did not provide full picture. After this discussion on devel I've linked, I spoke to Michael what changes would be in compliance with EDK2 driver model guidelines. An agreement was reached: Root Bridge driver that implements SIO Protocol and Serial I/O driver (with new entrypoint) that depends on SIO by DEPEX.

This way, driver would be a DXE Driver that runs new entrypoint only when SIO Protocol is present. I believe this approach doesn't violate UEFI Driver model rules since it uses standard DXE methods.

Also, the approach of modifying driver's entrypoint was suggested by Zhichao Gao.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118822): https://edk2.groups.io/g/devel/message/118822
Mute This Topic: https://groups.io/mt/105959587/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 1987 bytes --]

      reply	other threads:[~2024-05-10 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 13:09 [edk2-devel] [PATCH 0/1] MdeModulePkg: Load Serial driver in early DXE Borzeszkowski, Alan
2024-05-07 13:09 ` [edk2-devel] [PATCH 1/1] " Borzeszkowski, Alan
2024-05-08  3:27   ` Ni, Ray
2024-05-08 13:24     ` Borzeszkowski, Alan
2024-05-10  3:18       ` Ni, Ray
2024-05-10 15:03         ` Borzeszkowski, Alan [this message]

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=32021.1715353414607689205@groups.io \
    --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