All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linuxppc-dev@lists.ozlabs.org, jwboyer@linux.vnet.ibm.com
Subject: RFC: delete UART current-speed from 4xx DTS?
Date: Tue, 15 Sep 2009 10:31:36 -0400	[thread overview]
Message-ID: <20090915143135.GA7015@windriver.com> (raw)

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.

Looking at the Fsl boards, it seems that 99% of them don't list any
current-speed at all.  I'm willing to whip up a patch to delete them
from the various boards, but I thought I'd check 1st to see if there was
some other reasoning/input.  I suppose one could argue that u-boot
should be replacing the 9600 with 115k2 on the fly, but if the explicit
specification isn't helping anyone, then it probably just makes sense to
delete them anyway, I figured.

Here is the subset of boards I was considering deleting the lines from:

   bamboo.dts ebony.dts hcu4.dts holly.dts katmai.dts sam440ep.dts
   sequoia.dts taishan.dts walnut.dts yosemite.dts

Thanks,
Paul.

             reply	other threads:[~2009-09-15 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 14:31 Paul Gortmaker [this message]
2009-09-15 15:32 ` RFC: delete UART current-speed from 4xx DTS? 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
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=20090915143135.GA7015@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.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 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.