public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Piotr Perak <peri@aqua.aspd.pwr.wroc.pl>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1 not booting on 405CR
Date: Thu, 23 Sep 2004 21:08:57 +1000	[thread overview]
Message-ID: <1095937737.10779.2.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.21.0409231056010.24812-100000@aqua.aspd.pwr.wroc.pl>

On Thu, 2004-09-23 at 19:35, Piotr Perak wrote:
> Hi.
> 
> We already have 2.4.23 kernel working on our board using IBM 405CR
> processor. Now we're trying to start 2.6.8.1. But we have some strange
> problems.

I suggest you ask your question on the linuxppc-dev list (or better,
linuxppc-embedded, but that one was just re-created from the old
dead listserver so people may not be subscribed yet).

Look for those on http://ozlabs.org/mailman/listinfo

Ben.



      reply	other threads:[~2004-09-23 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23  9:35 2.6.8.1 not booting on 405CR Piotr Perak
2004-09-23 11:08 ` Benjamin Herrenschmidt [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=1095937737.10779.2.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peri@aqua.aspd.pwr.wroc.pl \
    /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