From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Scott Wood" <scottwood@freescale.com>
Cc: ppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: hang w/ppc6xx_defconfig related to 'simple-bus' compatible
Date: Wed, 6 Aug 2008 19:10:51 -0600 [thread overview]
Message-ID: <fa686aa40808061810h4ecf69bbj4f45082abd85d854@mail.gmail.com> (raw)
In-Reply-To: <20080806173547.GD3138@ld0162-tx32.am.freescale.net>
On Wed, Aug 6, 2008 at 11:35 AM, Scott Wood <scottwood@freescale.com> wrote:
> On Wed, Aug 06, 2008 at 07:41:28AM -0600, Grant Likely wrote:
>> On Tue, Aug 05, 2008 at 08:21:31AM -0500, Kumar Gala wrote:
>> > I'm trying to get the ppc6xx_defconfig booting on any 8641 (74xx/e600)
>> > system. If I remove the 'simple-bus' compatible from the soc node in
>> > the .dts it works. Otherwise it hangs at but and looks to be crashed in
>> > the serial driver due to accessing memory at 0.
>> >
>> > I've tried the same .dts (w/'simple-bus') using the
>> > mpc8641_hpcn_defconfig and things work.
>>
>> The Xilinx folks hit something similar. ns16550 nodes get matched if
>> the parent claims simple-bus. If extra stuff needs to be done to use
>> that port, then bad things happen.
>
> If extra stuff needs to be done, it shouldn't claim to be a simple-bus.
Heh, no, not the bus. :-) Extra stuff to use the serial device.
g.
prev parent reply other threads:[~2008-08-07 1:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 13:21 hang w/ppc6xx_defconfig related to 'simple-bus' compatible Kumar Gala
2008-08-06 13:41 ` Grant Likely
2008-08-06 13:47 ` Kumar Gala
2008-08-06 13:49 ` Grant Likely
2008-08-06 17:35 ` Scott Wood
2008-08-06 18:02 ` Stephen Neuendorffer
2008-08-06 18:39 ` Kumar Gala
2008-08-06 19:03 ` John Linn
2008-08-07 1:10 ` Grant Likely [this message]
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=fa686aa40808061810h4ecf69bbj4f45082abd85d854@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).