public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Piotr Król" <piotr.krol@3mdeb.com>
To: Laszlo Ersek <lersek@redhat.com>, edk2-devel@lists.01.org
Subject: Re: CorebootPayloadPkg: redirect UEFI Shell to serial
Date: Fri, 14 Jul 2017 01:53:13 +0200	[thread overview]
Message-ID: <5f50924b-c781-2715-2447-a7a94d571efb@3mdeb.com> (raw)
In-Reply-To: <c757d940-82be-a96a-4985-56344e7f1470@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 07/11/2017 08:01 PM, Laszlo Ersek wrote:

Hi Laszlo,
thanks for taking time to reply.

> 
> CorebootPayloadPkg/CorebootPayloadPkgIa32X64.dsc seems to correctly
> include the general SerialDxe driver:
> 
> # # ISA Support # MdeModulePkg/Universal/SerialDxe/SerialDxe.inf
> 
> and on top of that, the terminal and console drivers:
> 
> # # Console Support # 
> MdeModulePkg/Universal/Console/ConPlatformDxe/ConPlatformDxe.inf 
> MdeModulePkg/Universal/Console/ConSplitterDxe/ConSplitterDxe.inf 
> MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe.inf
>
>
> 
MdeModulePkg/Universal/Console/TerminalDxe/TerminalDxe.inf
> 
> I imagine SerialDxe is not configured correctly for the platform. 
> Can you look into the PCDs that SerialDxe consumes (see the INF 
> file),

Logs appear correctly in DXE and BDS, so at least at some point it
works. Boot logs for SHELL_TYPE=UEFI_BIN adn SHELL_TYPE=BUILD_UEFI:
http://81.95.197.197:7777/aciqabilaw
http://81.95.197.197:7777/ijopesosuy

It would be great to have the same for Shell application.

Board schematics is open and available here:
http://www.pcengines.ch/schema/apu2c.pdf
You can see that serial is exposed through LPC.

I tried to modify PcdSerialUseMmio to TRUE, but it doesn't seem to
affect anything. Linux say "ttyS0 at I/O 0x3f8", so using IO seems to
be fine.

> and/or whether 
> "CorebootModulePkg/Library/BaseSerialPortLib16550/BaseSerialPortLib16550.inf",
>
>
> 
which SerialDxe depends on in the CorebootPayloadPkg build, is
> appropriate for your hardware? (This lib instance also consumes a 
> large set of PCDs.)

I was able to get some results after removing:
DebugLib|MdePkg/Library/UefiDebugLibConOut/UefiDebugLibConOut.inf
from Shell.inf section in DSC. Boot log:
http://81.95.197.197:7777/isenazutac

As you can see I'm getting some logs from Shell entry point and it
looks like DoShellPrompt start, but it doesn't appear on serial. In
DoShellPrompt thing wait on ShellInfoObject.NewEfiShellProtocol->ReadFile
so it seems no input from serial is accepted.

Any further steps appreciated. I believe I need no stuff related to
GOP, maybe it cause some problems ?

Best Regards,
- -- 
Piotr Król
Embedded Systems Consultant
https://3mdeb.com | @3mdeb_com
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4DCbLYWmfoRjKeNLsu5x6WeqnkwFAlloB+kACgkQsu5x6Weq
nkxUJRAAn8vB7qYm7vvFiAU8n7YM3AkkJyWs0KoQOO/4vDqJU8/O3dgDsnOhMfa8
T4xD0w/DBRdn7l06IrEnGHrYq6qH7zXmY7H3+QU4J55off/LHqNYm1SwJ+8LCDU0
/3+8VKaG3j3SR+nw/+iYAK+jPRFC0CtRIT2eNseqRHyZyvVaBEs/gcmv0znHqAjS
rxkXc9VpkRbMq/dpoPpSbLtCf2D0d9G7QeyML4K+Kqhx66dnaKckUz7jS9amWE5b
diFH8rI9IzxugO4Yg/SQsGKnGdR2c4oOxiZbV+p8fbe/AyE5qB76V+YpM9bChB/0
5/kaiWrD4S4ucZH9mRb63Km4rFZV3Km2P0EWZvtaGNacIjvLoYH6kXlqDVemdDRQ
FxGhswPxDFYkhoXKN2TVUOVihKde37pkU2txDheQ60HdzcRl4uu3kSoX1g3j9gxe
+cDOv/K8GePbp6QRhVtOqz6qIsPbpffjucqnJ5fjKkHOqSFcj8d9hKhREoL5SbBW
YQXY9at0yLQWsvyOePcn5PFLxOpv6xr26KzLcAd6uKFMnxn64gXKZzrktJlY3VtQ
b2R57kADlluTLgpcprs2QSB/v1WSSQ9KLwV8FuoMAO4XyQ1S2mDQLQhbs70zJP+h
hcGK98Yqn0ItFinrOWT72sHUz35WUtUF8p9MdOd7eVxvcGLwwl4=
=qNsJ
-----END PGP SIGNATURE-----


  reply	other threads:[~2017-07-13 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 21:31 CorebootPayloadPkg: redirect UEFI Shell to serial Piotr Król
2017-07-11 18:01 ` Laszlo Ersek
2017-07-13 23:53   ` Piotr Król [this message]
2017-07-14  1:06     ` Laszlo Ersek
2017-07-15 13:00       ` Piotr Król
2017-07-25  9:16         ` Laszlo Ersek
2017-08-05  0:13           ` Piotr Król

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=5f50924b-c781-2715-2447-a7a94d571efb@3mdeb.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