From: "Richardson, Brian" <brian.richardson@intel.com>
To: Cameron Craig <Cameron.Craig@exterity.com>,
"'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Subject: Re: Missing FAB_D blobs when building devel-MinnowBoard3-UDK2017 for Leafhill CRB
Date: Thu, 18 Jan 2018 19:43:20 +0000 [thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AFA470E747@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <7e184be14e734ba79f23c5e3b4dc3f30@exterity.com>
Cameron: I saw the issue you filed in Bugzilla. That is the best method to track this request. Our team is reviewing the request and will reply there.
Thanks ... br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software
brian.richardson@intel.com -- @intel_brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Cameron Craig
Sent: Tuesday, January 16, 2018 4:55 AM
To: 'edk2-devel@lists.01.org' <edk2-devel@lists.01.org>
Subject: [edk2] Missing FAB_D blobs when building devel-MinnowBoard3-UDK2017 for Leafhill CRB
Hi all,
I'm currently looking at edk2-platforms/devel-MinnowBoard3-UDK2017 [1] as a potential bootloader for a Leafhill-based board.
With a few tweaks I've managed to build an image using the FAB_B blobs, but we're experiencing performance issues (very slow boot time from GRUB2 to Yocto Linux, signs of I/O bottleneck when booted).
The build scripts suggest that the FAB_D IFWI blobs are required for Leafhill, and I have noticed these are not available for download [2].
Is anyone able to provide the FAB_D IFWI blobs, or are there instructions available to produce the SpiChunk blobs from the standard IFWI image?
I'm hoping that the reason we're experiencing performance issues is because of the wrong IFWI blobs being used.
[1]: https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3-UDK2017
[2]: https://firmware.intel.com/projects/minnowboard3
Cheers,
Cameron
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
Exterity is a leading provider of IP Video and Digital Signage solutions that helps organizations to harness the power of video to communicate, educate and entertain. Our end-to-end solutions enable you to take TV and video content directly from any source and manage its delivery, live or on demand, to any connected device via your existing network. For more information or to schedule a product demonstration, contact Exterity on +44(0)1383 828 250 or visit www.exterity.com
Legal Notice
Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this e-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
Exterity Limited is registered in Scotland under No. 225313 with its registered office at St Davids House, St Davids Drive, Dalgety Bay, KY11 9NB
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-01-18 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 9:54 Missing FAB_D blobs when building devel-MinnowBoard3-UDK2017 for Leafhill CRB Cameron Craig
2018-01-18 19:43 ` Richardson, Brian [this message]
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=80AC2BAA3152784F98F581129E5CF5AFA470E747@ORSMSX114.amr.corp.intel.com \
--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