From: Matt Porter <mporter@kernel.crashing.org>
To: Piotr Perak <peri@aqua.aspd.pwr.wroc.pl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6.x on 405CR
Date: Tue, 28 Sep 2004 09:43:27 -0700 [thread overview]
Message-ID: <20040928094327.B1532@home.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0409281735560.6394-100000@aqua.aspd.pwr.wroc.pl>; from peri@aqua.aspd.pwr.wroc.pl on Tue, Sep 28, 2004 at 05:47:57PM +0200
On Tue, Sep 28, 2004 at 05:47:57PM +0200, Piotr Perak wrote:
> On Tue, 28 Sep 2004, Matt Porter wrote:
> > Hrm, I see. Did your firmware change between your working 2.4 kernel
> > and your non-working 2.6 kernel? If you're failing in there that would
> > be my first thought. I suppose that's probably not that case though.
>
> 2.4.23 still runs on board I try to port 2.6.8.1 to. So I guess firmware
> is not the problem?
In that case, it shouldn't be.
> > then you're an interesting spot. Can you trace it down to the exact
> > failure in __alloc_bootmem_core?
> I already did it. Can you please read
> http://ozlabs.org/pipermail/linuxppc-dev/2004-September/000104.html? I
> described there what weird things are happening in __alloc_bootmem_core.
I see. Can you move the reset instruction to isolate the offending
instruction?
BTW, it's not clear how you are guaranteeing that the processor has
bit 2 or 3 asserted before the dbcr0 load. If you preloaded r12 out of
the scope of the code fragments shown, it's clear that r12 is getting
clobbered in the subf instruction of the 2.6.8.1 fragment.
Is this a hobby project or a "for profit" project? If it's for profit,
then consider investing in a JTAG emulator (like BDI2000)...it'll pay
for itself many times over.
-Matt
next prev parent reply other threads:[~2004-09-28 16:43 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
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 [this message]
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=20040928094327.B1532@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@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).