From: Philippe Gerum <rpm@xenomai.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] I-pipe 2.6.12-v0.9-02
Date: Wed, 20 Jul 2005 13:37:00 +0000 (UTC) [thread overview]
Message-ID: <loom.20050720T152317-881@post.gmane.org> (raw)
In-Reply-To: <200507181244.40583.gene.heskett@verizon.net>
Gene Heskett <gene.heskett <at> verizon.net> writes:
>
> On Monday 18 July 2005 09:41, Philippe Gerum wrote:
> >The interrupt pipeline patch v0.9-02 has been released, fixing a
> > latency spot and a bug in the deferred printk() mechanism.
> >
> >A split version of the patch for x86, ppc32 and ia64 is available
> > here: http://download.gna.org/adeos/patches/v2.6/ipipe/split/
> >
> >Patch sequence to build a Linux 2.6.12 tree with I-pipe support:
> >
> >http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.tar.bz2
> >http://download.gna.org/adeos/patches/v2.6/ipipe/ipipe-2.6.12-v0.9-0
> >2.patch
>
> Will this then work with emc? emc, when run, loads the adeos stuff,
> then unloads it when its stopped. emc being the linux cnc machine
> controller.
>
> If it will, I'd like to play with it on a bdi-4.20 install.
>
> Or is this a seperate patch?
>
This will be a separate patch against the I-pipe, adding the missing bits to
support what emc and the like need, in order to run the real-time extension they
rely on. The I-pipe patch series consists of largely reworked Adeos patches only
retaining the interrupt pipeline code from its ancestor. We need a few other
things to support what those real-time extension need to fully cooperate with
Linux (which goes beyond just interposing on interrupts actually).
--
Philippe.
prev parent reply other threads:[~2005-07-20 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 13:41 Philippe Gerum
2005-07-18 16:44 ` Gene Heskett
2005-07-20 13:37 ` Philippe Gerum [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=loom.20050720T152317-881@post.gmane.org \
--to=rpm@xenomai.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®