All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
To: Sean Machin <smachin1000@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] How to build Xenomai 3 for TI AM3352 3.2.0 kernel based system?
Date: Sat, 13 Jun 2015 22:54:40 +0200	[thread overview]
Message-ID: <0e5d24055756fd9a9ce52e172eacbc60.squirrel@sourcetrek.com> (raw)
In-Reply-To: <CAO8ajWdaJFqnAqYM4rjZEse3j8gmUkOk5tZN_8DZrqNPadmx8w@mail.gmail.com>


Sean Machin wrote:
> Hi All,
>
> I'm very interested in trying out Xenomai on my custom ARM HF Linux
> system.  This system has been designed using the 3.2 Linux kernel, with
> vendor patches provided by TI.  The system is stable, and working well.
>
> After downloading the latest Xenomai code from git, I went to try and
> re-build the existing kernel with Xenomai.  I was going to run this
> command:
>
> scripts/prepare-kernel.sh
> --linux=~/src/kernel/cortex/linux-3.2.0-psp05.06.00.00
> --ipipe=~/xenomai-3/kernel/cobalt/arch/arm/patches/xxx --arch=arm
>
> But I can't find a patch file for my 3.2.0 kernel.  I also looked in
> http://download.gna.org/adeos/patches/v3.x/arm/older/ but can't find one
> their either.
>
> How can I get Xenomai to work for my system?  Upgrading our system to a
> newer kernel would be a lot of work and what we have now is stable and
> working well.

There used to be an I-pipe patch for Linux 3.2, but it was removed because
it was known to cause memory corruption and it was never fixed. You could
probably do some speleology in the git repository to find the patch that
fixed this issue in later kernels and backport it to the I-pipe for Linux
3.2.

-- 
                                            Gilles.
https://click-hack.org



      reply	other threads:[~2015-06-13 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 20:15 [Xenomai] How to build Xenomai 3 for TI AM3352 3.2.0 kernel based system? Sean Machin
2015-06-13 20:54 ` Gilles Chanteperdrix [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=0e5d24055756fd9a9ce52e172eacbc60.squirrel@sourcetrek.com \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=smachin1000@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.