public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Benjamin Doron" <benjamin.doron00@gmail.com>
To: Nate DeSimone <nathaniel.l.desimone@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [GSoC 2022] Introducing myself & seeking for project ideas
Date: Mon, 23 May 2022 09:50:25 -0700	[thread overview]
Message-ID: <28907.1653324625343525442@groups.io> (raw)
In-Reply-To: <MW4PR11MB582159C33D49A5CFB7BEAD2ACDEC9@MW4PR11MB5821.namprd11.prod.outlook.com>

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

Hi Theo and Nate,
I took a brief look at this myself, because having an emulated environment would help me with my project. I didn't know then that QemuOpenBoardPkg was an accepted project this year. OvmfPkg is large, I'm unfamiliar with QEMU's codebase and I'm only minimally familiar with Intel's old ICH chipsets (the platform some emulators expose), so I looked at porting QEMU's Q35 + ICH9 support into SimicsOpenBoardPkg. I don't know how you're preparing, but I'd recommend at least a look there: Q35's ICH9 and Simics' ICH10 are fairly similar. There are other QEMU machines, but I can't comment on those.

SimicsOpenBoardPkg can partially boot QEMU with a minimum of changes. It makes it into the DXE phase (where we'd eventually get a shell), but fails to initialise SMM, so it can't load the variable driver in there. Many drivers depend on the variable protocol, including critical UEFI-architecture ones, so the DXE core will assert and hang after printing a bunch of "driver GUID discovered but not loaded" messages. To fix this, the SMM access, maybe SMM control drivers would need to be patched; some register definitions differ between chipsets.

Anyways, I can send you my diff if you'd like, or you're welcome to approach this any way you'd like. SimicsOpenBoardPkg is not a true MinPlatform board because it implements a number of init steps itself rather than using some of MinPlatform's FSP-centric libraries. I'm probably going to skip to the step where I try Frankensteining enough MinPlatform code in to suffice my testing.

Best regards,
Benjamin

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

  reply	other threads:[~2022-05-23 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 19:35 [GSoC 2022] Introducing myself & seeking for project ideas Théo Jehl
2022-03-31 15:04 ` [edk2-devel] " Pedro Falcato
2022-04-02 12:01   ` Théo Jehl
2022-04-04 21:12     ` Pedro Falcato
2022-04-07 21:36       ` Nate DeSimone
2022-04-08 16:05         ` Théo Jehl
2022-04-13 23:15           ` Nate DeSimone
2022-05-23 16:50             ` Benjamin Doron [this message]
2022-05-23 17:33               ` Pedro Falcato
2022-05-23 18:14                 ` Oram, Isaac W
2022-05-24  5:54                 ` Gerd Hoffmann

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=28907.1653324625343525442@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