# RE: hang w/ppc6xx\_defconfig related to 'simple-bus' compatible

- From: Stephen Neuendorffer \<hidden\>
- Date: 2008-08-06 18:02:11 
- List: linuxppc-dev
- Page: https://ratatoskr.run/linuxppc-dev/2008/08/9444250
- Thread: https://ratatoskr.run/linuxppc-dev/2008/08/9444153/t.md

```text

The problem (in my case) is that the legacy-serial driver doesn't accept
all of the 16550 configurations accepted by the regular ns16550 driver.
The problem is not related to simple-bus, but only became visible when
simple-bus bindings are used because the legacy-serial driver
specifically looks for an ns16550 node contained by a simple-bus.

Most likely the hpcn_defconfig disables the legacy-serial driver
altogether.

Steve

> -----Original Message-----
> From: <redacted>
[mailto:linuxppc-dev-
> bounces+stephen.neuendorffer=3Dxilinx.com@ozlabs.org] On Behalf Of Scott
Wood
> Sent: Wednesday, August 06, 2008 10:36 AM
> To: <redacted>
> Cc: ppc-dev list
> Subject: Re: hang w/ppc6xx_defconfig related to 'simple-bus'
compatible
> =

> 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.
> =

> -Scott
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev


This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.
```