From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Stefan Roese <stefan.roese@gmail.com>
Cc: mfornero@aanddtech.com, Xenomai@xenomai.org
Subject: Re: [Xenomai] Porting Ipipe to new ARM SoC (Xilinx Zynq)
Date: Sun, 10 Feb 2013 15:23:22 +0100 [thread overview]
Message-ID: <5117AD5A.1080504@xenomai.org> (raw)
In-Reply-To: <50F3DD9A.9050306@gmail.com>
On 01/14/2013 11:27 AM, Stefan Roese wrote:
> Hi Matthew,
>
> On 01/12/2013 06:21 PM, mfornero@aanddtech.com wrote:
>> I'm looking for recommendations on how to best port ipipe support to a
>> new ARM SoC. The SoC has started to show up in mainline, but many of
>> the features haven't made it over yet. Xilinx maintains a git repo
>> here:
>>
>> git://git.xilinx.com/linux-xlnx.git
>>
>> And it look like they've synced with mainline 3.6
>>
>> The two approaches I've considered were either trying to port ipipe to
>> stock 3.6 (or at least the generic and ARM bits) or trying to backport
>> the Xilinx code to 3.5.3. I started with the later approach, but some
>> changes to the common clock architecture between 3.5 and 3.6 make this
>> somewhat difficult.
>>
>> Any thoughts on which approach would be better?
>
> I'm also working on supporting Zynq in I-pipe. My approach was to use
> the Xilinx 3.5.0 code version (git tag "xilinx-14.3-build2"). And port
> the I-pipe version from Gilles git repository to it. I still need to do
> some cleanup then I can send you the latest version.
Hi Stefan, Matthew,
I do not know if you managed to get the I-pipe working on Zynq.
You may have missed it, but it may be very important for debugging the
issues you encounter with the I-pipe port on Zynq, printk from primary
domain in I-pipe patches for Linux 3.4 and 3.5 does not work. So, if
you are debugging with printk, it may lead you to false conclusions.
You should apply the following patch (it has been pushed in the
for-core-3.5.7 branch of the ipipe-gch git):
diff --git a/arch/arm/kernel/smp.c b/arch/arm/kernel/smp.c
index 3b86167..f77ef11 100644
--- a/arch/arm/kernel/smp.c
+++ b/arch/arm/kernel/smp.c
@@ -440,7 +440,7 @@ void __ipipe_ipis_alloc(void)
return;
/* __ipipe_first_ipi is 0 here */
- ipi_nr = IPI_IPIPE_FIRST + IPIPE_LAST_IPI;
+ ipi_nr = IPI_IPIPE_FIRST + IPIPE_LAST_IPI + 1;
for (virq = IPIPE_IPI_BASE; virq < IPIPE_IPI_BASE + ipi_nr; virq++) {
_virq = ipipe_alloc_virq();
--
Gilles.
next prev parent reply other threads:[~2013-02-10 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 17:21 [Xenomai] Porting Ipipe to new ARM SoC (Xilinx Zynq) mfornero
2013-01-14 10:27 ` Stefan Roese
2013-01-22 0:00 ` mfornero
2013-01-22 7:55 ` Gilles Chanteperdrix
2013-01-23 0:27 ` mfornero
2013-01-23 2:00 ` Gilles Chanteperdrix
2013-01-23 3:43 ` Matthew Fornero
2013-01-23 7:02 ` Gilles Chanteperdrix
2013-01-23 23:51 ` mfornero
2013-01-24 9:03 ` Gilles Chanteperdrix
2013-01-24 23:57 ` mfornero
2013-01-25 9:01 ` Gilles Chanteperdrix
[not found] ` <OFC84FDBBF.88E9186F-ON85257AFC.007B4CC3-85257AFC.008309FB@LocalDomain>
2013-01-24 0:12 ` mfornero
2013-02-10 14:23 ` Gilles Chanteperdrix [this message]
2013-02-13 17:57 ` mfornero
2013-02-13 18:14 ` Stefan Roese
2013-02-13 18:38 ` mfornero
2013-02-14 8:19 ` Stefan Roese
2013-02-13 19:44 ` Gilles Chanteperdrix
2013-02-14 19:41 ` Gilles Chanteperdrix
2013-02-14 19:42 ` Gilles Chanteperdrix
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=5117AD5A.1080504@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai@xenomai.org \
--cc=mfornero@aanddtech.com \
--cc=stefan.roese@gmail.com \
/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.