From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from Internet2.beckhoff.com (Internet2.beckhoff.com [194.25.186.210]) by mx.groups.io with SMTP id smtpd.web08.6264.1649166342227960750 for ; Tue, 05 Apr 2022 06:45:42 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: beckhoff.com, ip: 194.25.186.210, mailfrom: c.koehne@beckhoff.com) Received: from 172.17.2.171 by Internet2.beckhoff.com (Tls12, Aes256, Sha384, DiffieHellmanEllipticKey256); Tue, 05 Apr 2022 13:45:39 GMT Received: from ex04.beckhoff.com (172.17.5.170) by ex05.beckhoff.com (172.17.2.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.24; Tue, 5 Apr 2022 15:45:38 +0200 Received: from ex04.beckhoff.com ([fe80::c545:54e6:8481:2958]) by ex04.beckhoff.com ([fe80::c545:54e6:8481:2958%6]) with mapi id 15.01.2375.024; Tue, 5 Apr 2022 15:45:38 +0200 From: =?UTF-8?B?Q29ydmluIEvDtmhuZQ==?= To: Gerd Hoffmann CC: "virtualization@freebsd.org" , Ard Biesheuvel , Jiewen Yao , Jordan Justen , Rebecca Cran , Peter Grehan , "devel@edk2.groups.io" Subject: Re: [PATCH] OvmfPkg: reserve igd memory by E820 Thread-Topic: [PATCH] OvmfPkg: reserve igd memory by E820 Thread-Index: AQHYR+4gR0J1mf/cg0yeubefYjkNkKzff6AAgAAoPdCAAR4jgIAAJajQgAAEWgCAAGS8EA== Date: Tue, 5 Apr 2022 13:45:38 +0000 Message-ID: References: <20220404063448.280-1-c.koehne@beckhoff.com> <20220404113830.6novz55zpid3l6fl@sirius.home.kraxel.org> <20220405070639.uq5uiydxhirwu4gb@sirius.home.kraxel.org> <7de01ae500554923941dc5ff9e537637@beckhoff.com> <20220405093700.ahsezswbumjlg3au@sirius.home.kraxel.org> In-Reply-To: <20220405093700.ahsezswbumjlg3au@sirius.home.kraxel.org> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.204.203] x-olx-disclaimer: EX05.BECKHOFF.COM MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, > > I don't know if it's possible to extract it from host firmware within > > OS context easily. > > Extracting from firmware updates is probably easier. Good idea but I'll focus on the rest first because I have access to the GOP driver for my systems. > > According to Intel you should ask your board manufacturer. > > I'm wondering why if the opregion initialization (which actually is > board-specific) is not done by the gop driver. >>From my experience and as far as I know, Intels GOP driver seems to be platform independent. I think only Intel can tell us why. > > > Once we have the code for vgabios and PlatformGopPolicy we can roll t= hem > > > with the intelgop driver into a rom image with EfiRom. Ideally also = add > > > opregion content to the rom somehow. > > > > Sounds good. Does these EFI drivers have to be maintained outside of > > EDKII? > > Hosting this in https://github.com/tianocore/edk2-staging is probably > one option (not fully sure about the policy there). > > Creating a separate project for that might also make sense given that > the roms will not be generic but host-specific, so end-users will have > to install the tools needed to collect host-specific bits and to build > the final rom image. I'm going to start working on that locally. Maybe while working on it, I'll have an idea where's the best place to maintain it. Best regards Corvin Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans Bec= khoff Registered office: Verl, Germany | Register court: Guetersloh HRA 7075