From: ghannon@cspi•com
To: Kim Phillips <kim.phillips@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: .dtb file for mpc8641_hpcn failing on recent kernel/u-boot.
Date: Tue, 20 May 2008 09:41:49 -0400 [thread overview]
Message-ID: <8525744F.004ADF6D.00@pine.cspi.com> (raw)
Thank-You Kim,
That got me beyond where I was.
It's now having problems with the SATA setup, but I will stare at
that for a while, and see if there is anything on the mailing list about
it.
It actually made it past the PCI Scan which was one of the
key things I needed to see anyway.
Gary
Kim Phillips <kim.phillips@freescale•com> on 05/19/2008 06:03:37 PM
To: Gary Hannon/CSP
cc: linuxppc-dev@ozlabs•org
Subject: Re: .dtb file for mpc8641_hpcn failing on recent kernel/u-boot.
On Mon, 19 May 2008 22:57:29 +0000 (UTC)
Gary Hannon <ghannon@cspi•com> wrote:
> Am I missing a flag on the dtc?
try adding -R 8 -S 0x3000 to the dtc command line.
Kim
next reply other threads:[~2008-05-20 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 13:41 ghannon [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-19 22:57 .dtb file for mpc8641_hpcn failing on recent kernel/u-boot Gary Hannon
2008-05-19 23:03 ` Kim Phillips
2008-05-20 16:35 ` Timur Tabi
2008-05-20 16:42 ` Scott Wood
2008-05-20 16:43 ` 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=8525744F.004ADF6D.00@pine.cspi.com \
--to=ghannon@cspi$(echo .)com \
--cc=kim.phillips@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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