public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Kurt Kennett <Kurt.Kennett@microsoft.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
	"Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: Headless devices - BDS to use?
Date: Mon, 14 Nov 2016 18:49:32 +0100	[thread overview]
Message-ID: <ff596a7d-03b0-80ce-9da8-34ca552c265c@redhat.com> (raw)
In-Reply-To: <CY1PR03MB2345353F67C6A2E1FDAF2D039CBC0@CY1PR03MB2345.namprd03.prod.outlook.com>

On 11/14/16 18:21, Kurt Kennett wrote:
> Okay, but there is no reference or example for such, correct?

Sorry, I was too terse. Yes, there are at least two examples. Please see OvmfPkg/OvmfPkgX64.dsc or ArmVirtPkg/ArmVirtQemu.dsc.

It seems (from a build report) that BdsDxe inherits a depex of

  gEfiHiiStringProtocolGuid AND
  gEfiHiiDatabaseProtocolGuid AND
  gEfiHiiConfigRoutingProtocolGuid

from the "MdeModulePkg/Library/UefiHiiServicesLib/UefiHiiServicesLib.inf" library instance.

These protocols are provided if you include "MdeModulePkg/Universal/HiiDatabaseDxe/HiiDatabaseDxe.inf" in your platform DSC.

> 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?

I think the following section from ArmVirtQemu.dsc can be used well enough as an example:

  #
  # Bds
  #
  [...]
  MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe.inf
  MdeModulePkg/Universal/SetupBrowserDxe/SetupBrowserDxe.inf
  MdeModulePkg/Universal/DriverHealthManagerDxe/DriverHealthManagerDxe.inf
  MdeModulePkg/Universal/BdsDxe/BdsDxe.inf
  MdeModulePkg/Logo/LogoDxe.inf
  MdeModulePkg/Application/UiApp/UiApp.inf {
    <LibraryClasses>
      NULL|MdeModulePkg/Library/DeviceManagerUiLib/DeviceManagerUiLib.inf
      NULL|MdeModulePkg/Library/BootManagerUiLib/BootManagerUiLib.inf
      NULL|MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib.inf
  }

I'm sure Ray (CC'd) will be able to advise you better.

I assume Nt32Pkg and EmulatorPkg should be possible examples too.

> And there is no boot manager menu that is not graphics based?

The above set of drivers provides a dialog / form based setup utility (incl. boot manager) that works well on serial. Also, IIRC the BCFG command can be used from the UEFI shell.

Thanks
Laszlo

> 
> 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
>>
> 



      parent reply	other threads:[~2016-11-14 17:49 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
2016-11-14 17:41         ` Kinney, Michael D
2016-11-14 17:54         ` Laszlo Ersek
2016-11-14 17:49     ` Laszlo Ersek [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=ff596a7d-03b0-80ce-9da8-34ca552c265c@redhat.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