public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Benjamin Doron" <benjamin.doron00@gmail.com>
To: Oram, Isaac W <isaac.w.oram@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] MinPlatform Board port (GSoC 2021)
Date: Sat, 22 May 2021 08:32:13 -0700	[thread overview]
Message-ID: <13149.1621697533827079707@groups.io> (raw)
In-Reply-To: <MW3PR11MB4747956FCA73878480330788D02A9@MW3PR11MB4747.namprd11.prod.outlook.com>

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

Hi Isaac,
Thanks for the document. I've seen the main MinPlatform document before, which also outlines control flow, but this shows a quick overview of it all. I'll look for the MinPlatform porting training links too. Thanks.

> 
> 
> 
> I would also make sure that you have the board information you need. 
> Whatever datasheets and such that are required.
> 
> 
> 
> In addition to the Minimum Platform spec, I like to have the UEFI Spec and
> the UEFI Platform Initialization arch specs handy for reference.  ACPI
> too.
> 
> 
> 
> That gives you the HW and SW documents.  And you have mentors and the
> mailing list for a network of experts.  Those plus hardware and tools
> should set you up.  Minimum tools capabilities should be flash programming
> and serial debug.
> 
> 

I have the schematics, boardview and the datasheets that became relevant to porting (some I was unable to find, mainly regarding PCIe devices). While this board may have a working serial pad, it would be difficult to access and likely requires soldering (which I cannot do).

I planned to skip directly to stage 4 (OS), or at least 3 (shell). I should have the required board knowledge from my coreboot port. For debug logs, I think the serial port library which logs Status Codes (which will be stored in memory) could be a good fit. For early problems in PEI, I see there is a serial port library which logs to SPI flash. If these fail here, I'll have to hope the USB3 debugging feature will work.

> 
> 
> 
> I will defer to Nate on communication recommendations as all the GSoC
> projects will be working those out.  And I have to admit I didn’t read the
> GSoC documentation thoroughly yet.
> 
> 

Okay, not a problem.

Nice to meet you!

Best regards,
Benjamin Doron

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

  reply	other threads:[~2021-05-22 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 23:28 MinPlatform Board port (GSoC 2021) Benjamin Doron
2021-03-31 23:58 ` [edk2-devel] " Nate DeSimone
2021-04-04  4:45   ` Benjamin Doron
2021-04-06  8:54     ` Nate DeSimone
2021-04-08 17:32       ` Benjamin Doron
2021-04-09  8:01         ` Nate DeSimone
2021-04-12 18:34           ` Benjamin Doron
2021-04-13  0:46             ` Nate DeSimone
2021-05-19 23:44               ` Benjamin Doron
2021-05-20  1:13                 ` Oram, Isaac W
2021-05-22 15:32                   ` Benjamin Doron [this message]
     [not found] ` <167192C821638254.25167@groups.io>
2021-04-01 15:56   ` Nate DeSimone

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