From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Remco den Breeje <remco@vioco.nl>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] ARM I-pipe patch for 3.1+ kernels
Date: Thu, 21 Jun 2012 22:33:23 +0200 [thread overview]
Message-ID: <4FE38513.2080607@xenomai.org> (raw)
In-Reply-To: <CA+K6ZL0db_K0NsuEcKrQO9rcJ4myrx6QVge6i7HyMEkDhkwWww@mail.gmail.com>
On 06/21/2012 10:14 PM, Remco den Breeje wrote:
> Hi Gilles et.al.,
>
> I'm interested in running a Xenomai patched system on a Raspberry Pi
> computer[1] that compromises a ARM11 CPU (ARMv6 architecture). The Linux
> kernels supported on the Raspberry are either Linux 3.1 or 3.2 [2,3], while
> the most recent ARM ipipe patch is written for a 3.0 kernel. Looking at
> your ipipe git[4], there hasn't been ARM related work for more recent
> kernels.
> What are the changes of a forward port, rebased on 3.1 or 3.2 kernels? Are
> there underlying technical difficulties?
>
> I'm aware that even if there was a >3.0 ARM patch available, the Raspberry
> specific code needs to be ported. However, being a ARM-newby, porting board
> specific code together with porting the ipipe code is one step too far ;)
The ipipe branch core-3.2 supports kernel 3.2 on arm. Note however that
a lot of things have changed in this patch version, so the I-pipe
porting guide is completely helpless.
More generally, the git repository with the current work on the arm
architecture is:
http://git.xenomai.org/ipipe-gch.git
The branch for kernel x.y is for-ipipe-x.y-arm
--
Gilles.
next prev parent reply other threads:[~2012-06-21 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 20:14 [Xenomai] ARM I-pipe patch for 3.1+ kernels Remco den Breeje
2012-06-21 20:32 ` Philippe Gerum
2012-06-21 20:33 ` Gilles Chanteperdrix [this message]
2012-06-21 21:40 ` Remco den Breeje
2012-06-22 6:57 ` Remco den Breeje
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=4FE38513.2080607@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=remco@vioco.nl \
--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.