From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail05.groups.io (mail05.groups.io [45.79.224.7]) by spool.mail.gandi.net (Postfix) with ESMTPS id 5D5C77803CC for ; Mon, 6 Jan 2025 00:57:35 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=m923b9VOa1L4rCgKUDApvNNBnSPtYBnl61pc/RB2UXQ=; c=relaxed/simple; d=groups.io; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Thread-Index:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Resent-Date:Resent-From:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Language; s=20240830; t=1736125055; v=1; x=1736384253; b=NHks4RZ0hEdXa86xkoIEbk1JIe0w0st+fMc7oUiHHMuZlU9cG+JS/eo2b5U3/Lu1zPc78Zi6 xpHnFSAYNM5F4K0NLIngAKGi4BW92X90XgSRi+M7TzWh2whNs9JQaTdKnrOwfScWzPendN0LN1l 4NADahE6/3Peqr5mBZEGzpgplV8XRzQUQlGbK8/P78TuJD/H1ow8ZNXuFPZd5NpwE0xaIn9H8aa abTU9r1BELZYgvdPJDrHpNUX+85CqYd9cKeh9DhozOP85Pcac2JmDycNfBGR5XdwIhQ5rdHadPo rgbmiaN8ZRmDT6v2i1GkPt5C+2oA2DaykLaE9WqB9QKVw== X-Received: by 127.0.0.2 with SMTP id 7IQIYY7687511xoULNEAwnMY; Sun, 05 Jan 2025 16:57:33 -0800 X-Received: from cxsh.intel-email.com (cxsh.intel-email.com [121.46.250.151]) by mx.groups.io with SMTP id smtpd.web11.49988.1736125050290220343 for ; Sun, 05 Jan 2025 16:57:32 -0800 X-Received: from cxsh.intel-email.com (localhost [127.0.0.1]) by cxsh.intel-email.com (Postfix) with ESMTP id 6C45DDDA7A6 for ; Mon, 6 Jan 2025 08:57:26 +0800 (CST) X-Received: from localhost (localhost [127.0.0.1]) by cxsh.intel-email.com (Postfix) with ESMTP id 67C27DDA7A4 for ; Mon, 6 Jan 2025 08:57:26 +0800 (CST) X-Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by cxsh.intel-email.com (Postfix) with SMTP id 7DCA0DDA79E for ; Mon, 6 Jan 2025 08:57:22 +0800 (CST) X-Received: from DESKTOPS6D0PVI ([58.246.60.130]) (envelope-sender ) by 192.168.6.13 with ESMTP(SSL) for ; Mon, 06 Jan 2025 08:57:21 +0800 X-WM-Sender: gaoliming@byosoft.com.cn X-Originating-IP: 58.246.60.130 X-WM-AuthFlag: YES X-WM-AuthUser: gaoliming@byosoft.com.cn From: "gaoliming via groups.io" To: , References: In-Reply-To: Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0gQ29tcGF0aWJpbGl0eSBvZiBQQ0llIFVFRkkgb3B0aW9uIFJPTQ==?= Date: Mon, 6 Jan 2025 08:57:22 +0800 Message-ID: <002001db5fd5$f1d73fd0$d585bf70$@byosoft.com.cn> MIME-Version: 1.0 Thread-Index: AQFfKlrNLr6J6LbOF0ZrdLljrKVrtbQBVpaw Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Resent-Date: Sun, 05 Jan 2025 16:57:32 -0800 Resent-From: gaoliming@byosoft.com.cn Reply-To: devel@edk2.groups.io,gaoliming@byosoft.com.cn List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: X-Gm-Message-State: bmG6jVK1zVg5AY31PGmUAkCSx7686176AA= Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01DB6018.FFFBB850" Content-Language: zh-cn X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20240830 header.b=NHks4RZ0; dmarc=pass (policy=none) header.from=groups.io; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 45.79.224.7 as permitted sender) smtp.mailfrom=bounce@groups.io ------=_NextPart_000_0021_01DB6018.FFFBB850 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable UEFI Option Rom only consumes the protocols defined in UEFI spec, it doesn= =E2=80=99t depend on other protocols.=20 =20 Thanks Liming =E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io = =E4=BB=A3=E8=A1=A8 =E4=B8=B0=E7=AB=8B=E6=B3=A2 via groups.io =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2025=E5=B9=B41=E6=9C=883=E6=97=A5 17:= 45 =E6=94=B6=E4=BB=B6=E4=BA=BA: devel =E4=B8=BB=E9=A2=98: [edk2-devel] Compatibility of PCIe UEFI option ROM =20 Hello, =20 PCIe option ROM is an UEFI driver, basiclly. You can build an PCIe option= ROM with any UEFI development kits, EDKII or AMI Aptio, burn a flash chip = mounted on PCIe plugin card. At the moment of DXE driver dispatching, PCIe = option ROM loads and runs in the UEFI enviroment of motherboard. The mother= board UEFI could be built with other UEFI development kits, the compatibilt= y issue could occur.=20 This actully happened in a project of ours: A PCIe network Option ROM is = built with AMI UEFI development kits, having the driver health functionalit= y. This PCIe network card plugin an EDKII UEFI motherboard, enter Setup uti= lity, check the driver health, something is not working: a PopupBox was sup= posed to pop, but didn't. and many ASSERT are send out, reporting VFR STRIN= G can't be found. I think the PCIe network Option ROM is using AMI-specific= protocols and string resouces that are totally absent in the EDKII executi= on enviroment. Meanwhile, I look up the EDKII-implemented protocols, many EDKII_** prefi= xed protocols exist, these are not UEFI specified. Think about this situati= on: I build a PCIe option ROM with EDKII, using EDKII_FORM_DISPLAY_ENGINE_P= ROTOCOL, then plugin the PCIe card in an AMI UEFI motherboard, the PCIe opt= ion ROM can't locate the EDKII_FORM_DISPLAY_ENGINE_PROTOCOL, probably. Some= thing is not working, either.=20 Making things worse, it is impossible for PCIe card vendors to deliver va= riants, it is impossible for the end-user to choose a proper variant as wel= l. Now, how can we address this issue? Best Regards Feng Libo =20 -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#120955): https://edk2.groups.io/g/devel/message/120955 Mute This Topic: https://groups.io/mt/110449204/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- ------=_NextPart_000_0021_01DB6018.FFFBB850 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

UEFI Option Rom only consumes the protocols defined in UEF= I spec, it doesn=E2=80=99t depend on other protocols.

 

= Thanks

Liming

=E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io <devel@edk2.groups.io>= = =E4=BB=A3=E8=A1=A8 =E4=B8=B0=E7=AB=8B=E6=B3=A2 via grou= ps.io
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:= 2025=E5=B9=B41=E6=9C=883=E6=97=A5 17:45=E6=94=B6=E4=BB=B6=E4=BA=BA: devel <devel@edk2.groups.io>
=E4=B8=BB=E9= =A2=98: [edk2-devel] Compa= tibility of PCIe UEFI option ROM

 

Hello,

 

  PCIe option ROM is an UEFI driver, basiclly. Y= ou can build an PCIe option ROM with any UEFI development kits, EDKII or AM= I Aptio, burn a flash chip mounted on PCIe plugin card. At the moment of DX= E driver dispatching, PCIe option ROM loads and runs in the UEFI enviroment= of motherboard. The motherboard UEFI could be built with other UEFI develo= pment kits, the compatibilty issue could occur.

  This actully happene= d in a project of ours: A PCIe network Option ROM is built with AMI UEFI de= velopment kits, having the driver health functionality. This PCIe network c= ard plugin an EDKII UEFI motherboard, enter Setup utility, check the driver= health, something is not working: a PopupBox was supposed to pop, but didn= 't. and many ASSERT are send out, reporting VFR STRING can't be found. I th= ink the PCIe network Option ROM is using AMI-specific protocols and string = resouces that are totally absent in the EDKII execution enviroment.<= span lang=3DEN-US style=3D'font-size:10.5pt;font-family:"Source Han Sans",s= erif'>

  M= eanwhile, I look up the EDKII-implemented protocols, many EDKII_** prefixed= protocols exist, these are not UEFI specified. Think about this situation:= I build a PCIe option ROM with EDKII, using EDKII_FORM_DISPLAY_ENGINE_PROT= OCOL, then plugin the PCIe card in an AMI UEFI motherboard, the PCIe option= ROM can't locate the EDKII_FORM_DISPLAY_ENGINE_PROTOCOL, probably. Somethi= ng is not working, either.

<= p class=3DMsoNormal>  Making things worse, it is impossible for= PCIe card vendors to deliver variants, it is impossible for the end-user t= o choose a proper variant as well.



Now, how can we address this is= sue?



Best Regards



<= div>

Feng Libo

=  

_._,_._,_
Groups.io Links:

=20 You receive all messages sent to this group. =20 =20

View/Reply Online (#120955) | =20 | Mute= This Topic | New Topic
Your Subscriptio= n | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_
------=_NextPart_000_0021_01DB6018.FFFBB850--