From: Philippe Gerum <rpm@xenomai.org>
To: Michael Galea <michaelgalea@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Enable I-PIPE - kernel boot hangs in mpc836x_mds
Date: Thu, 22 May 2008 10:48:00 +0200 [thread overview]
Message-ID: <48353340.9090306@domain.hid> (raw)
In-Reply-To: <48349D40.9070707@domain.hid>
Michael Galea wrote:
> I'm trying to bring xenomai up on an Freescale mpc836x_mds board. I'm
> using the ipipe-2.6.24-powerpc-2.1-02 branch of the git tree at Denx.
>
> The kernel boots fine with ipipe disabled, nfs root mounting its file
> system. But as soon as I enable ipipe in the kernel I get..
>
> ...
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> IP-Config: Complete:
> device=eth0, addr=10.128.10.234, mask=255.0.0.0, gw=10.128.0.253,
> host=10.128.10.234, domain=, nis-domain=(none),
> bootserver=10.128.10.10, rootserver=10.128.10.10, rootpath=
> Looking up port of RPC 100003/2 on 10.128.10.10
> irq 33, desc: c02746c0, depth: 0, count: 0, unhandled: 0
> irq 33, desc: c02746c0, depth: 0, count: 0, unhandled: 0
>
> And it hangs. Since this is the place where the kernel usually finds
> its PHY, I might suspect its an issue with that..
>
Something may be missing in the IPIC code to fully support the interrupt
pipeline too. A dump of /proc/interrupts when the board boots properly would
help here.
> I'm currently trying to get Denx's 2.6.20 branch running but its
> freezing after loading the device tree, so I have some issues there.
>
> Can anyone having success with this board report what kernel they are using?
>
> Thanks
>
--
Philippe.
prev parent reply other threads:[~2008-05-22 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 22:08 [Xenomai-help] Enable I-PIPE - kernel boot hangs in mpc836x_mds Michael Galea
2008-05-22 8:48 ` Philippe Gerum [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=48353340.9090306@domain.hid \
--to=rpm@xenomai.org \
--cc=michaelgalea@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.