linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Piotr Perak <peri@aqua.aspd.pwr.wroc.pl>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 2.6.x on 405CR
Date: Mon, 27 Sep 2004 06:57:58 -0700	[thread overview]
Message-ID: <20040927065758.B25288@home.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0409271244030.8658-100000@aqua.aspd.pwr.wroc.pl>; from peri@aqua.aspd.pwr.wroc.pl on Mon, Sep 27, 2004 at 12:46:07PM +0200

On Mon, Sep 27, 2004 at 12:46:07PM +0200, Piotr Perak wrote:
> Hi.
> 
> Anyone seen 2.6.x kernel working on 405CR?
> I can't make it boot.

I can't recall anybody around here having a 405CR.  That's probably
why you didn't get a reponse the first time you posted this.

Since you are failing in ocp_add_one_device() and you have a
processor which doesn't have a chip definition in 2.6, the
problem is probably somewhere there.  Doublecheck your
arch/ppc/platforms/4xx/ibm405cr.c (you do have one, right?)
against a known good one in arch/ppc/platforms/4xx/ibm405gp.c

I wish I could rent you my BDI2000 to speed up your debugging,
but we're too far away from each other. :)

-Matt

  reply	other threads:[~2004-09-27 13:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 10:46 2.6.x on 405CR Piotr Perak
2004-09-27 13:57 ` Matt Porter [this message]
2004-09-27 14:10   ` Jon Masters
2004-09-27 15:16     ` Matt Porter
2004-09-27 16:24   ` Piotr Perak
2004-09-28  9:57   ` Piotr Perak
2004-09-28 13:44     ` Matt Porter
2004-09-28 15:47       ` Piotr Perak
2004-09-28 16:43         ` Matt Porter
2004-09-28 17:00           ` Mark Chambers
2004-09-29 11:20           ` Piotr Perak
2004-09-29 11:58             ` Jon Masters
2004-09-29 13:22               ` Mark Chambers
2004-09-29 14:22                 ` Jon Masters
2004-09-27 15:19 ` Matt Porter

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=20040927065758.B25288@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).