All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "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 10:51:56 -0700	[thread overview]
Message-ID: <4E835EBC.3080604@linux.intel.com> (raw)
In-Reply-To: <20110927225722.54936878@lxorguk.ukuu.org.uk>

Hi Alan,

Thanks for the suggestions. Still not working, details follow.

On 09/27/2011 02:57 PM, Alan Cox wrote:
>> Using the ti_usb_3410_5052 driver with modified vendor/product strings, I am
>> able to get ttyUSB0 on my host and open it in minicom:
>>
>> $ sudo modprobe ti_usb_3410_5052 vendor_3410=0x0451 product_3410=0x5053
>> $ minicom -D /dev/ttyUSB0
> 
> Please submit those idents to GregKH for the ti_usb driver.
> 

I will. I need to confirm this is something I can do now (if I can use
the product name, etc.).

>> Can anyone offer up some ideas on what I might try to get:
>>
>> 1) the getty working
>> 2) the earlier kernel messages to appear
>> 3) syslinux working
>>
>> over the serial port?
> 
> It may depend a lot on the port. If it boots in PCI D3 (power saved) then
> it's going to be fun. Otherwise forcing the address of the port ought to
> do the trick.
> 
> See	
> 	console=uart8250,io 0xb060,115200n8

I tried:

console=uart8250,io,0xb060,115200n8

With this I got 4 non-ascii chars

> 
> although it's polled so you may want to drop the speed a bit!

I switched all my terminal emulators, syslinux config, the getty, and
console redirection in the bios to use 9600n8. Then ran with:

console=uart8250,io,0xb060,9600n8

This printed several bursts of garbled non-ascii strings, but did so
very early! :)

With minicom on each end, I see the INT 18 count go up by 1 for every
char sent from the board and up by 3 for every char sent from my dev
box, as well as the irregular rx,fe increment mentioned originally.

> 
> netconsole might also be useful to debug the early serial problems !

I did give that a shot, it complained about eth0 not existing, despite
the driver being compiled in. Possibly an init race with netconsole and
pch_gbe? Similar posts sent to linux-next earlier this year.


> 
> No idea for syslinux.

Doesn't like 9600 either.

> 
> Alan

So I'm bugging the hardware/firmware guys, really looks like something
is bad under the covers to me.

Thanks Alan!

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

  reply	other threads:[~2011-09-28 17:51 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 [this message]
2011-09-28 19:14     ` Bjorn Helgaas
2011-09-28 19:33       ` Darren Hart

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=4E835EBC.3080604@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.