From: "David H. Lynch Jr." <dhlii@dlasys•net>
To: grave@ipno•in2p3.fr, linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: porting linux ppc on custom board, stuck in timer loop ?
Date: Mon, 28 Nov 2005 01:48:25 -0500 [thread overview]
Message-ID: <438AA839.4040006@dlasys.net> (raw)
Xavier;
I am having/had the exact same problem on a Xilinx VI based system and 2.6.12-2.6.14.2
I was eventually able to resolve it by removing MSR_ME from MSR_KERNEL. After that I have been able to successfully boot through to
starting init where I am hanging now. I beleive I do not have a working timer and that may be related to the problem with Machine Check Exceptions.
Were you ever able to resolve your problem aside from switching to 2.4.20, and if so what solution did you come up with ?
>Hi !
>I still try to port linux ppc on our ppc405 based hardware, after a look
>at xilinx_ml300.c file that gives the list of function calls I wait for
>a call to start_kernel but I found that start_kernel is never reached...
>In fact the code in head_4xx.S jumps to 0x00001000 which is Decrementer
>exception :
>/* Now turn on the MMU for real! */
> lis r4,MSR_KERNEL at h <https://ozlabs.org/mailman/listinfo/linuxppc-dev>
> ori r4,r4,MSR_KERNEL at l <https://ozlabs.org/mailman/listinfo/linuxppc-dev>
> lis r3,start_kernel at h <https://ozlabs.org/mailman/listinfo/linuxppc-dev>
> ori r3,r3,start_kernel at l <https://ozlabs.org/mailman/listinfo/linuxppc-dev>
> mtspr SPRN_SRR0,r3
> mtspr SPRN_SRR1,r4
> rfi /* enable MMU and jump to start_kernel */
> b . /* prevent prefetch past rfi */
>Is this my hardware implementation that is incorrect ? Or I missed
>something in my kernel configuration ?
>Thanks in advance for any answer...
>xavier
next reply other threads:[~2005-11-28 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 6:48 David H. Lynch Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-28 13:10 porting linux ppc on custom board, stuck in timer loop ? Xavier Grave
2005-06-28 15:01 ` Xavier Grave
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=438AA839.4040006@dlasys.net \
--to=dhlii@dlasys$(echo .)net \
--cc=dhlii@comcast$(echo .)net \
--cc=grave@ipno$(echo .)in2p3.fr \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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