All of lore.kernel.org
 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: Thu, 10 Jan 2008 13:19:58 -0600	[thread overview]
Message-ID: <47866FDE.5070307@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B03D99E60@ismail.innsys.innovsys.com>

Rune Torgersen wrote:
> Not sure what was wrong. We took a step back, and redid some stuff, and
> now we have serial output from the boot-wrapper.
> THe checkstop came from the wrapper grying to access the bcsr and doing
> the chip select fixup. We don';t have a bcsr on our board, and the cs
> layout is different.

There's no bcsr access in the upstream bootwrapper (the mention of bcsr 
in cuboot-pq2.c is just one reason why some boards require us to do the 
CS programming), and the CS programming is chip-level, not board-level 
(it just requires that the device tree have a correct localbus node for 
the board).

-Scott

  reply	other threads:[~2008-01-10 19:20 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
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 [this message]
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=47866FDE.5070307@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 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.