All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Marco Cavallini <rtai@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Future of fusion
Date: Thu, 13 Oct 2005 10:24:13 +0200	[thread overview]
Message-ID: <434E19AD.4030500@domain.hid> (raw)
In-Reply-To: <000d01c5cfcb$8b5dfaf0$0600a8c0@domain.hid>

Marco Cavallini wrote:
> Hello,
> I'd like to know (if is possible) the future plans and task schedule of 
> fusion into xenomai project.
> TIA

There are things already going on "under the surface" right now, and others that 
would depend on everyone's input in order to start them or not. The roadmap will 
clearly depend on the combination of both aspects. I will give some details 
shortly about the current or next-to-be-started efforts, but the feedback part 
is important too, so here is the call for discussion once posted to this list:

--

I propose that we start discussing along the following lines, going into deeper 
detail as needed, but in any case, please remember that we don't have infinite 
resources to do everything at once, and that we need to keep an organisation 
that fits our abilities to manage it, so let's keep it modest and efficient. If 
I missed some important issues, please jump in. After that initial work, we 
should be able to define a sensible roadmap.

- Regular automated benchmarking: What is Xenomai currently capable of, how 
stable is it, do we progress or regress over time and releases, arch by arch?

- Documentation effort, dissemination: I'm a potential new user, do I have some 
unambiguous source of information available to get my feet wet with Xenomai?

- Architecture ports: There is life beyond x86.

- Kernel ports: Is there still room for a 2.4 port?

- Configuration, building and packaging issues: Could we make this easier?

- Linux integration issues: Tools we should interface with, features we should 
make more seamless.

- Scalability: Is Xenomai scalable enough? What's missing?

- Drivers: Now that we have a deeply integrated port of RTDM, what's next? Field 
busses and other industrial gizmos anyone?

- Current interfaces: Are we happy with them?

- New skins: Any new colors for the "chameleon"?

-- 

Philippe.


  parent reply	other threads:[~2005-10-13  8:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13  7:55 [Xenomai-core] Future of fusion Marco Cavallini
2005-10-13  8:15 ` Jan Kiszka
2005-10-13  8:24 ` Philippe Gerum [this message]
2005-10-13  8:37   ` Herman Bruyninckx
2005-10-13  8:50     ` Gilles Chanteperdrix
2005-10-13  8:54       ` Herman Bruyninckx
2005-10-13  9:12         ` Philippe Gerum
2005-10-13  9:34           ` Herman Bruyninckx
2005-10-13 13:57             ` Jan Kiszka
2005-10-13 19:57             ` Gilles Chanteperdrix
2005-10-13  9:46     ` Jan Kiszka
2005-10-13 10:46   ` Paul
2005-10-13 13:33     ` Philippe Gerum
2005-10-13 19:47       ` Wolfgang Grandegger
2005-10-13 20:28     ` Gilles Chanteperdrix
2005-10-14  3:42       ` Romain Lenglet
2005-10-16  7:47         ` [Xenomai-core] Packaging issues and licensing issues Romain Lenglet
2005-10-16  7:50           ` Gilles Chanteperdrix
2005-10-16 14:00             ` gna-dev
2005-10-16 14:18               ` Romain Lenglet
2005-10-17 18:54               ` Gilles Chanteperdrix

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=434E19AD.4030500@domain.hid \
    --to=rpm@xenomai.org \
    --cc=rtai@domain.hid \
    --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.