From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC8377 system bring up
Date: Fri, 8 Oct 2010 13:05:06 -0500 [thread overview]
Message-ID: <4CAF5D52.2020600@freescale.com> (raw)
In-Reply-To: <1286555567.6933.52.camel@swa-m460>
Andr? Schwarz wrote:
>
>
> Are there any obvious issues I have missed so far ?
Nothing obvious to me. I haven't done much work at this level of U-Boot
bring-up, but I would think that failure to assert LCS0 points to a LAWBAR
problem. Perhaps you have overlapping LAWs?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-10-08 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 16:32 [U-Boot] MPC8377 system bring up André Schwarz
2010-10-08 18:05 ` Timur Tabi [this message]
2010-10-08 18:25 ` André Schwarz
2010-10-08 18:26 ` Timur Tabi
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=4CAF5D52.2020600@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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.