linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: newest "bk pull" of 8xx tree still builds a kernel that hangs
Date: Mon, 7 Jun 2004 17:25:27 -0700	[thread overview]
Message-ID: <20040608002527.GA14242@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0406071950460.3449@localhost.localdomain>


On Mon, Jun 07, 2004 at 08:04:44PM -0400, Robert P. J. Day wrote:
> On Mon, 7 Jun 2004, Tom Rini wrote:
> > On Mon, Jun 07, 2004 at 11:55:33AM -0400, Robert P. J. Day wrote:
> >
> > >
> > >   having just got back from vacation, i may have missed some of the latest
> > > developments.  i just did a "bk pull" from the linuxppc-2.5 tree, rebuilt
> > > the kernel for my 8xx board and, just like before i left, the kernel hung
> > > almost immediately upon booting:
> > >
> > > Linux/PPC load: console=ttyS0,9600 rw root=/dev/ram0 init=/sbin/minit
> > > Uncompressing Linux...done.
> > > Now booting the kernel
> > > (hang)
> > >
> > > should i be expecting this?  once upon a time, of course, i got all the
> > > way to user space before the hang.  have there been some recent patches to
> > > cause this latest behaviour?  i haven't messed with the config file in
> > > quite some time.  should i?
> >
> > What probably happened is that you don't have a UART driver selected.
> > I've had my best luck with CONFIG_SERIAL_CPM, so you might want to try
> > that.
>
> i selected that, but still no luck -- kernel still hangs almost
> immediately -- but there may be other issues here.
[snip]

I haven't had time to look into this yet, in part because I just don't
know how well to trust my h/w, but to get SMC1 console working (RPX
Lite) I need to enable both SCC1 and SMC1.  For your board, I would
recommend enabling all of the consoles.

And in case others were wondering, the old driver has a different set of
issues, at least on my hw, it doesn't see input (and/or it causes a
livelock at boot, I haven't tried again in a while).

--
Tom Rini
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-08  0:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 15:55 newest "bk pull" of 8xx tree still builds a kernel that hangs Robert P. J. Day
2004-06-07 20:08 ` Tom Rini
2004-06-08  0:04   ` Robert P. J. Day
2004-06-08  0:25     ` Tom Rini [this message]
2004-06-08  0:28       ` Robert P. J. Day
2004-06-08  0:45         ` Tom Rini
2004-06-08  0:56           ` Robert P. J. Day

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=20040608002527.GA14242@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rpjday@mindspring.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).