From: Jacob Burkholder <jake.burkholder2@gmail.com>
To: edk2-devel@lists.01.org
Subject: SerialDxe with BaseSerialPortLib16550 and standard PC com port
Date: Tue, 19 Mar 2019 19:06:24 -0700 [thread overview]
Message-ID: <CAOE-m4CLK1-NWnMoBNp1V1=kW+XYuPe2nq36fOLDPnE0CvxpzA@mail.gmail.com> (raw)
Greetings!
I had trouble using SerialDxe.efi with BaseSerialPortLib16550 on a standard
PC com port (com1). The PC is an asrock motherboard running whatever EFI
bios it came with. I changed MdeModulePkg.dsc so that
BaseSerialPortLib16550 would be used instead of BaseSerialPortLibNull and
then rebuilt SerialDxe.efi and loaded and started it using
BootServices->{LoadImage,StartImage}.
Output works but input doesn't work, typed characters aren't received by
the uart. I looked at the code briefly and it seems like the uart isn't
initialized properly. I used this script to get input working (the
commands should be self explanatory, they're not efi shell commands though):
image SerialDxe.efi
outb 0x3fb 0x83
outw 0x3f8 1
outb 0x3fb 0x3
outb 0x3fc 0x3
Any chance it can be fixed upstream?
Thanks,
Jake
next reply other threads:[~2019-03-20 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 2:06 Jacob Burkholder [this message]
2019-03-20 19:05 ` SerialDxe with BaseSerialPortLib16550 and standard PC com port Kinney, Michael D
2019-03-21 1:33 ` Jacob Burkholder
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='CAOE-m4CLK1-NWnMoBNp1V1=kW+XYuPe2nq36fOLDPnE0CvxpzA@mail.gmail.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