From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: John.Linn@xilinx.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: of_serial vs legacy serial support with powerpc arch on 405
Date: Tue, 11 Mar 2008 17:02:55 -0500 [thread overview]
Message-ID: <20080311170255.4866e51a@zod.rchland.ibm.com> (raw)
In-Reply-To: <20080311150430.153AD3D8066@mail134-sin.bigfish.com>
On Tue, 11 Mar 2008 09:04:27 -0600
"John Linn" <John.Linn@xilinx.com> wrote:
> I've searched and found some threads, but it's still not clear to me.
> I'm working on 405 with powerpc and trying to get UART550 working.
Walnut works. So do Halakeau and Kilauea. Is your serial port
significantly different from those?
> I know that I need speed, freq, and reg-shift properties in the device
> tree and I have found patches for of_serial.c.
Patches for of_serial.c for what?
> I still don't understand when to use of_serial.c (SERIAL_OF_PLATFORM) vs
> the legacy support for serial ports. Is there any docs that I'm not
> finding that I should read?
There are no docs. At one time, of_serial was declared as the one true
serial driver, but these days either will do. The benefit of
legacy_serial is that output is enabled earlier in the boot.
> I don't see a way to configure in the legacy support, but I'm using
> SERIAL_OF and having problems. I don't see the console getting enabled
> even though it found the serial port driver.
You need to have CONFIG_PPC_UDBG_16550 set to bring in legacy_serial.
josh
next prev parent reply other threads:[~2008-03-11 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 15:04 of_serial vs legacy serial support with powerpc arch on 405 John Linn
2008-03-11 22:02 ` Josh Boyer [this message]
2008-03-11 22:14 ` Stephen Neuendorffer
2008-03-11 22:23 ` John Linn
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=20080311170255.4866e51a@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=John.Linn@xilinx.com \
--cc=linuxppc-dev@ozlabs.org \
/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).