public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: "Richardson, Brian" <brian.richardson@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Lu, ShifeiX A" <shifeix.a.lu@intel.com>,
	"Zimmer, Vincent" <vincent.zimmer@intel.com>,
	Andrew Fish <afish@apple.com>, "Wei, David" <david.wei@intel.com>
Subject: Re: Improvements to build system etc. for edk2-platforms devel-MinnowBoard3?
Date: Wed, 22 Feb 2017 09:52:41 -0700	[thread overview]
Message-ID: <2d7462e9-de6c-67b2-ffd7-a3fa194ce06b@bluestop.org> (raw)
In-Reply-To: <80AC2BAA3152784F98F581129E5CF5AF6655EC20@ORSMSX114.amr.corp.intel.com>

On 2/22/2017 9:34 AM, Richardson, Brian wrote:
> Thanks for the input. For future reference, you can use the TianoCore Bugzilla to report issues on any EDK II feature/platform. https://github.com/tianocore/tianocore.github.io/wiki/Reporting-Issues
>
> I agree the readme.md should be present, and use markup instead of plain text to work better in github. You can open an issue on this in Bugzilla.
>
> Normally, we ask folks to change the number of processor threads based on their system configuration. We don't add a larger thread number by default, but it might be good to set it '5' by default (assuming a dual core processor with hyperthreading) instead of '1' (assuming a single core system w/o threading). I don't know if this will cause any compatibility issues on older systems, but it's worth a check.
>
> At this time, MinnowBoard 3 build is only validated in Windows. That's why there is no equivalent .sh file for BuildBIOS yet, but it will be added once Linux build is verified and checked in.

I'm more about _fixing_ issues I find rather than reporting them! Are 
you saying that patches wouldn't be welcome just now?  Is there a reason 
why you don't want to make full use of the CPU while building? And I 
understand that MinnowBoard 3 only builds under Windows at the moment, 
but if more of it built using python (and python is already listed as a 
prerequisite in the ReadMe file) the porting might be simpler.

-- 
Rebecca


  reply	other threads:[~2017-02-22 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  1:20 Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? Rebecca Cran
2017-02-22  4:50 ` Gao, Liming
2017-02-22  5:11   ` Andrew Fish
2017-02-22  5:48   ` Rebecca Cran
2017-02-22  7:35     ` Gao, Liming
2017-02-22 16:34     ` Richardson, Brian
2017-02-22 16:52       ` Rebecca Cran [this message]
2017-02-22 19:10         ` Richardson, Brian
2017-02-23  2:49           ` Wei, David
2017-02-23 18:53             ` Brian J. Johnson
2017-02-23 19:10               ` Rebecca Cran
2017-02-23 23:11                 ` Richardson, Brian

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=2d7462e9-de6c-67b2-ffd7-a3fa194ce06b@bluestop.org \
    --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