From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: RFC: delete UART current-speed from 4xx DTS?
Date: Wed, 16 Sep 2009 07:44:07 +1000 [thread overview]
Message-ID: <1253051047.8375.232.camel@pasglop> (raw)
In-Reply-To: <20090915153220.GG12372@zod.rchland.ibm.com>
On Tue, 2009-09-15 at 11:32 -0400, Josh Boyer wrote:
> On Tue, Sep 15, 2009 at 10:31:36AM -0400, Paul Gortmaker wrote:
> >One of the guys here was getting a messed up console on a bamboo board
> >(on linux boot), which he traced to the fact that the default dts has a
> >9600 baudrate coded into it (board was running 115k2, not 9600). Either
> >deleting the line, or replacing the 9600 with zero fixed the problem.
>
> Once booted, was there a valid current-speed property in /proc/device-tree
> for the serial node? I'm curious if U-Boot created it, or if the kernel
> just used whatever baud was present already.
>
> When I did the bamboo port a while ago, I recall having issues with either
> a missing clock-frequency or current-speed (or both perhaps) and the bootloader
> on the board was the original PIBS. It might have been an issue with PIBS
> but I'm guessing the rest of the 4xx boards copied from either Ebony or
> Bamboo in their ports and hence contain that property.
I think I recently added code to legacy_serial probe the speed from the
HW if the property is absent, which should help.
Cheers,
Ben.
next prev parent reply other threads:[~2009-09-15 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 14:31 RFC: delete UART current-speed from 4xx DTS? Paul Gortmaker
2009-09-15 15:32 ` Josh Boyer
2009-09-15 19:32 ` Paul Gortmaker
2009-09-15 20:02 ` Josh Boyer
2009-09-15 20:44 ` Paul Gortmaker
2009-09-15 21:44 ` Benjamin Herrenschmidt [this message]
2009-09-16 13:19 ` Josh Boyer
2009-09-16 14:57 ` Paul Gortmaker
2009-09-16 21:31 ` Benjamin Herrenschmidt
2009-09-17 1:44 ` Josh Boyer
2009-09-23 18:15 ` Josh Boyer
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=1253051047.8375.232.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul.gortmaker@windriver.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).