All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Ran Shalit <ranshalit@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] kernel 3.12
Date: Mon, 25 Apr 2016 10:36:44 -0400	[thread overview]
Message-ID: <20160425143644.GI11630@csclub.uwaterloo.ca> (raw)
In-Reply-To: <CAJ2oMh+vab29mm8xhMc=3KT=2mG2cO=opi5jtJtTkc_wFugU3A@mail.gmail.com>

On Sun, Apr 24, 2016 at 10:21:50AM +0300, Ran Shalit wrote:
> We intend to use ipipe with zynq (we already have 3.12.0 kernel used with zynq).
> Do you think the patch should be relevant for zynq ?
> I see that xilinx have their own patch , but it is for older kernel 2.6.3
> http://www.wiki.xilinx.com/Xenomai+for+Zynq#Xenomai for Zynq-7000 AP
> SoC Linux--Patch

You can give it a try.  The zynq does have a Cortex-A9 as far as I recall,
so it ought to work.  Doesn't mean there aren't other bits that need
fixing in the zynq specific code.  But maybe there isn't.

Just remember it was never an officially supported kernel version.
It worked for us, it was given a once over by a proper xenomai developer
who did not seem to think it was wrong, but if it doesn't work I wouldn't
expect the xenomai developers to be excited to help fix it.

> I also see that in git there is ipipe for 3.12.0
> http://git.xenomai.org/ipipe-gch.git/log/?h=raw/for-ipipe-3.12.0
> But again I am unsure if it is relevant for zynq too.

Well that was a work in progress I believe and never officially released
as far as I recall.  I started from that one, but the one I posted is
actually based on the 3.14 patch and backported as far as I recall.
It has been a while since we moved to 3.14.

-- 
Len Sorensen


  reply	other threads:[~2016-04-25 14:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 12:46 [Xenomai] kernel 3.12 Ran Shalit
2016-04-18 13:45 ` Lennart Sorensen
2016-04-18 13:47   ` Ran Shalit
2016-04-18 13:54     ` Lennart Sorensen
2016-04-18 13:56       ` Ran Shalit
2016-04-18 14:28         ` Ran Shalit
2016-04-18 14:30           ` Lennart Sorensen
2016-04-24  7:21             ` Ran Shalit
2016-04-25 14:36               ` Lennart Sorensen [this message]
2016-04-25 16:38                 ` Ran Shalit
2016-04-25 17:08                   ` Lennart Sorensen
2016-04-25 19:50                   ` Gilles Chanteperdrix
2016-04-25 20:01                     ` Ran Shalit
2016-04-25 20:09                       ` Lennart Sorensen
2016-04-25 20:23                         ` Gilles Chanteperdrix
2016-04-25 21:31                           ` Lennart Sorensen
2016-04-25 21:42                             ` Gilles Chanteperdrix
2016-04-26  6:08                         ` Jan Kiszka
2016-04-26  5:48                     ` Ran Shalit

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=20160425143644.GI11630@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=ranshalit@gmail.com \
    --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.