linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Help with device tree binding for SMC serial
Date: Wed, 09 Jan 2008 16:40:45 -0600	[thread overview]
Message-ID: <47854D6D.2010906@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B03D58BEF@ismail.innsys.innovsys.com>

Rune Torgersen wrote:
>> From: Scott Wood
>> Don't forget to exclude the SMC parameter RAM from the muram 
>> data area 
>> in /soc/cpm/muram/data/reg.  If you have an older device tree binding 
>> that has no /soc/cpm/muram node, but instead has two resources in 
>> /soc/cpm/reg, you need to move to head-of-tree to get this to work.
> 
> Did that, now we get e checkstop resert. Time to hook up the
> BDI-2000....
> Is there a way to have the bootwrapper use the u-boot serial for a while
> (like a early srial port) for debugging?

If you mean calling into u-boot for a console, no, there's no code for that.

What do your cpm and muram nodes look like?

-Scott

  reply	other threads:[~2008-01-09 22:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 19:18 Help with device tree binding for SMC serial Rune Torgersen
2008-01-09 19:45 ` Scott Wood
2008-01-09 22:22   ` Rune Torgersen
2008-01-09 22:29     ` Scott Wood
2008-01-09 22:37       ` Rune Torgersen
2008-01-09 22:40         ` Scott Wood [this message]
2008-01-09 23:07           ` Rune Torgersen
2008-01-10 17:53             ` Scott Wood
2008-01-10 19:10               ` Rune Torgersen
2008-01-10 19:19                 ` Scott Wood
2008-01-11  0:07                   ` Rune Torgersen
2008-01-11 14:13                     ` Rune Torgersen
2008-01-11 17:24                       ` Scott Wood
2008-01-11 18:11                         ` Rune Torgersen
2008-01-11 18:15                           ` Scott Wood

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=47854D6D.2010906@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=runet@innovsys.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).