All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danrae Pray <danrae.pray@metecs.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] prepare-kernel.sh error on Ubuntu 14.04
Date: Thu, 2 Nov 2017 17:49:24 -0500	[thread overview]
Message-ID: <CAOocw5uCnv_iZKzA5eMPV1rOS1Rfc0wq=bEifxofd2n=zPL1zg@mail.gmail.com> (raw)
In-Reply-To: <0daa5cf3-7525-1e1c-a1c3-df76b66d29e5@xenomai.org>

Just wanted to note this ipipe patch appears to have worked.  Ran into an
issue w/ visorbus driver, but wasn't sure if I needed it (
https://xenomai.org/pipermail/xenomai/2016-February/035819.html) so
disabling the UNISYS SPAR option in kernel config seems to have fixed it...

Thanks!

On Wed, Nov 1, 2017 at 3:01 PM, Philippe Gerum <rpm@xenomai.org> wrote:

> On 11/01/2017 07:13 PM, Danrae Pray wrote:
> > Hi,
> >
> > I am trying to install the COBALT kernel alongside the Ubuntu 14.04
> kernel
> > in a VirtualBox VM and have executed the following script:
> >
> > ./scripts/prepare-kernel.sh --arch=x86_64 --linux=/usr/src/linux-4.4.95
> > --ipipe=/usr/src/ipipe-core-4.4.43-x86-8.patch
> >
> > The xenomai code and ipipe patch came from the xenomai downloads site and
> > the linux distro is from kernel.org...
> >
> > Can someone please help me understand why prepare-kernel.sh is failing?
> >
>
> Because some changes which happened between mainline kernel 4.4.43 and
> 4.4.95 are conflicting with those introduced by the I-pipe patch, which
> was originally based on 4.4.43.
>
> This patch against kernel 4.4.71 is available, you may want to try it
> instead. It will still apply to 4.4.95:
>
> http://xenomai.org/downloads/ipipe/v4.x/x86/ipipe-core-4.4.71-x86-10.patch
>
> --
> Philippe.
>

      reply	other threads:[~2017-11-02 22:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 18:13 [Xenomai] prepare-kernel.sh error on Ubuntu 14.04 Danrae Pray
2017-11-01 20:01 ` Philippe Gerum
2017-11-02 22:49   ` Danrae Pray [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='CAOocw5uCnv_iZKzA5eMPV1rOS1Rfc0wq=bEifxofd2n=zPL1zg@mail.gmail.com' \
    --to=danrae.pray@metecs.com \
    --cc=rpm@xenomai.org \
    --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.