From: Kurt Kennett <Kurt.Kennett@microsoft.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: Headless devices - BDS to use?
Date: Mon, 14 Nov 2016 17:36:21 +0000 [thread overview]
Message-ID: <CY1PR03MB234530D56C5EF6C82ED10C2F9CBC0@CY1PR03MB2345.namprd03.prod.outlook.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F564844305@ORSMSX113.amr.corp.intel.com>
But it is pulling in:
INF MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe.inf
INF MdeModulePkg/Universal/SetupBrowserDxe/SetupBrowserDxe.inf
Which are display based components. Are these required in the image even though they are not used?
A browser and display engine take up a lot of space on a constrained storage system.
K2
-----Original Message-----
From: Kinney, Michael D [mailto:michael.d.kinney@intel.com]
Sent: Monday, November 14, 2016 9:34 AM
To: Kurt Kennett <Kurt.Kennett@microsoft.com>; Laszlo Ersek <lersek@redhat.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Cc: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
Subject: RE: [edk2] Headless devices - BDS to use?
K2,
The QuarkPlatformPkg is an example of a serial only console platform that uses MdeModulePkg BDS.
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Kurt Kennett
> Sent: Monday, November 14, 2016 9:21 AM
> To: Laszlo Ersek <lersek@redhat.com>
> Cc: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> Subject: Re: [edk2] Headless devices - BDS to use?
>
> Okay, but there is no reference or example for such, correct?
>
> Right now people who don't have a display must fumble about trying to
> get Hii resources they don't need, understand, or use to get it to work?
>
> And there is no boot manager menu that is not graphics based?
>
> K2
>
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Monday, November 14, 2016 9:19 AM
> To: Kurt Kennett <Kurt.Kennett@microsoft.com>
> Cc: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> Subject: Re: [edk2] Headless devices - BDS to use?
>
> On 11/14/16 17:51, Kurt Kennett wrote:
> > What BDS are headless devices (no display, serial port only) supposed to use?
> >
> > The MdeModulePkg one seems to require Hii resources in order to work at all.
>
> It may require HII resources, but it works fine with just a serial port.
>
> Thanks
> Laszlo
>
> > The ArmPlatformPkg BDS (that supported headless devices just fine)
> > seems to be
> gone now.
> >
> > K2
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> >
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-11-14 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 16:51 Headless devices - BDS to use? Kurt Kennett
2016-11-14 17:18 ` Laszlo Ersek
2016-11-14 17:21 ` Kurt Kennett
2016-11-14 17:33 ` Kinney, Michael D
2016-11-14 17:36 ` Kurt Kennett [this message]
2016-11-14 17:41 ` Kinney, Michael D
2016-11-14 17:54 ` Laszlo Ersek
2016-11-14 17:49 ` Laszlo Ersek
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=CY1PR03MB234530D56C5EF6C82ED10C2F9CBC0@CY1PR03MB2345.namprd03.prod.outlook.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