From: Gailu Singh <gailu96@gmail.com>
To: Matthias Lange <matthias.lange@kernkonzept.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: 8250 memory mapped UART
Date: Wed, 1 Mar 2017 15:21:59 +0530 [thread overview]
Message-ID: <CAOifn+0Uo4ynFES0D+MCzSRhd0r65Ovhp=DCEUTn7h3_UOCiyg@mail.gmail.com> (raw)
In-Reply-To: <947f7550-489b-0d54-dd43-422f01fdc7c6@kernkonzept.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
My board is Intel Oxbohill CRB (Apollo lake). On my board UART are not
connected to PCI.
I am using grub2 payload loaded by coreboot. UART works fine in coreboot by
using memory mapped 8050 driver (
https://github.com/coreboot/coreboot/blob/master/src/drivers/uart/uart8250mem.c),
however when grub2 is loaded it refuses to recognize UART.
On Wed, Mar 1, 2017 at 3:08 PM, Matthias Lange <
matthias.lange@kernkonzept.com> wrote:
> Hi,
>
> On 03/01/2017 08:00 AM, Andrei Borzenkov wrote:
> > please test patches from Matthias Lange
> >
> > https://lists.gnu.org/archive/html/grub-devel/2017-02/msg00104.html
> >
> >
> > On Wed, Mar 1, 2017 at 9:15 AM, Gailu Singh <gailu96@gmail.com> wrote:
> >> Hi Experts,
> >>
> >> I am using GRUB2 on intel apollo lake board. This board does not have IO
> >> mapped uart instead it has 8250 memory mapped UART.
>
> Could you share some details about the board?
>
> >> GRUB2 does not recognize memory mapped uart and gives error ("serial
> port
> >> COM0 not found). There is a 8250 memory mapped driver available in
> coreboot.
> >> Is it possible to port that driver to Grub2?
>
> My patch set adds support for 8250 MMIO PCI cards. Is the UART on your
> board connected via PCI?
>
> Best,
> Matthias.
>
[-- Attachment #2: Type: text/html, Size: 2048 bytes --]
next prev parent reply other threads:[~2017-03-01 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 5:53 8250 memory mapped UART Gailu Singh
2017-03-01 6:15 ` Fwd: " Gailu Singh
2017-03-01 7:00 ` Andrei Borzenkov
2017-03-01 9:38 ` Matthias Lange
2017-03-01 9:51 ` Gailu Singh [this message]
2017-03-01 9:57 ` Gailu Singh
2017-03-01 10:32 ` Gailu Singh
2017-03-01 10:57 ` Matthias Lange
2017-03-01 11:04 ` Gailu Singh
2017-03-03 12:03 ` Gailu Singh
2017-03-03 13:41 ` Matthias Lange
2017-03-03 14:07 ` Gailu Singh
2017-03-24 17:29 ` Gailu Singh
2017-03-27 17:59 ` Gailu Singh
2017-03-27 18:31 ` Lennart Sorensen
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-all 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='CAOifn+0Uo4ynFES0D+MCzSRhd0r65Ovhp=DCEUTn7h3_UOCiyg@mail.gmail.com' \
--to=gailu96@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=matthias.lange@kernkonzept.com \
/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;
as well as URLs for NNTP newsgroup(s).