All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] v2.1 status
Date: Fri, 18 Nov 2005 14:01:02 +0100	[thread overview]
Message-ID: <437DD08E.1020202@domain.hid> (raw)
In-Reply-To: <437CB8BA.8040902@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

Philippe Gerum wrote:
> 
> Here is an update regarding the way things progress on the v2.1 branch:
> 
> o The build system has been deeply revamped, so that we now fully leave
> the burden of building Xenomai's kernel support to Linux. To this end,
> the code tree has been reorganized in two major sections, the first one
> contains the kernel-related sources (ksrc/), the other is hosting the
> user-space support (src/). Since the user-space portion does not need to
> know about the kernel sources anymore, several issues have been solved
> in the same move. All in all, things are way simpler than before, which
> seems to indicate that we are heading to the right direction. The
> documentation for the installation process needs to be updated though.
> 
> o Also as a matter of build system (and a bit more), v2.1 has been
> backported to Linux 2.4, starting with the ppc32 support. We rely on
> Denx's 2_4-devel tree as our 2.4 kernel of reference for this port [1].
> A second backport to 2.4/x86 will happen when this combo is I-pipe
> ready. We are ahead of schedule regarding this backport, since it was
> initially planned for Q12006, but since we are going to add more
> supported architectures in the next months, it's better to have a stable
> build system for that.
> 
> o PowerPC-wise (again), we should be close to ready for 2.6.15, since
> Heikki merged both the 32 and 64-bit trees in a single one.
> 
> All other tasks planned are undergoing. For my part, I'm going to fiddle
> now with ADI's Blackfin for which we already have the required Adeos
> support, and create the Xenomai port for it. Since this one is uClinux
> based, we should be able to check that the new build system is ok to
> host any kind of port sanely.
> 

Question: On recent roadmaps I'm so far missing the topic "RT-signal
support in userspace". Are there any concrete schedules (Qx 200y)?

I think to remember that you said Adeos would be involved in such an
extension. Maybe it would be a good time to think about this also when
we extend the Adeos API by shareable IRQs.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2005-11-18 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 17:07 [Xenomai-core] v2.1 status Philippe Gerum
2005-11-18 13:01 ` Jan Kiszka [this message]
2005-11-18 14:41   ` Philippe Gerum
2005-11-18 16:38     ` Ignacio García Pérez
2005-11-19 17:56       ` Philippe Gerum
2005-11-19 17:35 ` Wolfgang Grandegger
2005-11-19 18:28   ` Philippe Gerum

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=437DD08E.1020202@domain.hid \
    --to=kiszka@domain.hid \
    --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.