From: Philippe Gerum <rpm@xenomai.org>
To: "Steven A. Falco" <sfalco@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Compile-time bug, and problem with PPC440 ethernet
Date: Wed, 18 Jun 2008 18:17:41 +0200 [thread overview]
Message-ID: <48593525.2040103@domain.hid> (raw)
In-Reply-To: <4857BBCD.6020902@domain.hid>
Steven A. Falco wrote:
> Philippe Gerum wrote:
>> Steven A. Falco wrote:
>>
>>> I am building kernel 2.6.25.4 from DENX with Xenomai 2.4.4 for PPC440EPx
>>> (sequoia development board).
>>>
>>> The kernel tries to use DHCP to obtain network settings. With IPIPE
>>> disabled, this works perfectly. However, when I enable IPIPE, the board
>>> sends packets ok, but does not receive packets - I can see the DHCP with
>>> a sniffer, but the development board does not receive them.
>>
>>
>> External interrupts are probably locked out by the pipeline engine;
>> I've fixed a
>> similar issue in recent patches for other PICs. Which I-pipe patch
>> release are
>> you using?
>
>
> I am using the patch that came with Xenomai 2.4.4, namely:
> adeos-ipipe-2.6.25-powerpc-DENX-2.2-02.patch
>
I can't reproduce this issue on a 440EP board, but I still have to to put my
hands on a 440EPX to check this. However, both should be using the common 44x
PIC support, so I don't expect big changes here.
Are you using the powerpc/ branch, or legacy ppc/ one for building the sequoia
kernel?
--
Philippe.
next prev parent reply other threads:[~2008-06-18 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 18:57 [Xenomai-core] Compile-time bug, and problem with PPC440 ethernet Steven A. Falco
2008-06-16 21:56 ` Steven A. Falco
2008-06-17 7:30 ` Philippe Gerum
2008-06-17 13:27 ` Steven A. Falco
2008-06-18 16:17 ` Philippe Gerum [this message]
[not found] ` <48594232.5020505@domain.hid>
2008-06-18 17:20 ` Philippe Gerum
[not found] ` <48594CC9.4030408@domain.hid>
2008-06-19 8:16 ` Philippe Gerum
2008-06-26 12:57 ` Steven A. Falco
2008-06-26 13:07 ` Philippe Gerum
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=48593525.2040103@domain.hid \
--to=rpm@xenomai.org \
--cc=sfalco@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.