From: Darren Hart <dvhart@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"lkml," <linux-kernel@vger.kernel.org>,
Denis Turischev <denis@compulab.co.il>,
Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Subject: Re: Serial issues with EG20T (Topcliff) PCH uarts
Date: Wed, 28 Sep 2011 12:33:13 -0700 [thread overview]
Message-ID: <4E837679.4040904@linux.intel.com> (raw)
In-Reply-To: <CAErSpo6XcctMq1uM2No8Z=1_sgBxBhNQ3os3dU=aHCsPxrpwBg@mail.gmail.com>
On 09/28/2011 12:14 PM, Bjorn Helgaas wrote:
> On Wed, Sep 28, 2011 at 11:51 AM, Darren Hart <dvhart@linux.intel.com> wrote:
>>
>> Hi Alan,
>>
>> Thanks for the suggestions. Still not working, details follow.
>>
>> On 09/27/2011 02:57 PM, Alan Cox wrote:
>>>
>>> No idea for syslinux.
>>
>> Doesn't like 9600 either.
>
> Are you using "serial 1" or similar for the syslinux config? I don't
> know how syslinux learns the (port -> address) mapping, but
> doc/syslinux.txt says you can also specify the address directly, e.g.,
> "serial 0xb060 9600".
I was using 0,1,2,3, with no output. Using serial 0xb060 as you describe
results in a single char appearing in minicom when syslinux tries to
output to the serial port.
>
> I'm not familiar with the EG20T hardware, but all the code in
> drivers/tty/serial/pch_uart.c makes me wonder how 16550-compatible
> those things really are. If the EG20T UARTs require special tickling,
> syslinux isn't likely to know how to do that.
I the results of the test above support this concern. Syslinux
apparently couldn't find the ports by itself. Specifying the IO address
directly gets it to the right place, but something appears to not be
initialized.
I wonder if this could be fixed with some help from the firmware.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-09-28 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 18:02 Serial issues with EG20T (Topcliff) PCH uarts Darren Hart
2011-09-27 21:57 ` Alan Cox
2011-09-28 17:51 ` Darren Hart
2011-09-28 19:14 ` Bjorn Helgaas
2011-09-28 19:33 ` Darren Hart [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-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=4E837679.4040904@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bhelgaas@google.com \
--cc=denis@compulab.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=tomoya-linux@dsn.okisemi.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