From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] RFC: 2.5 todo list.
Date: Fri, 02 Oct 2009 19:48:32 +0200 [thread overview]
Message-ID: <4AC63CF0.7090001@domain.hid> (raw)
In-Reply-To: <1254505304.2703.347.camel@domain.hid>
Philippe Gerum wrote:
>> Ok. So, if we add the core skin fdtable, this leaves us with two items:
>> - signals in primary domain
>> - core skin fdtable
>>
>
> Ack. Add the following I-pipe stuff as well:
>
> - nios2 design upgrade. Those FPGA thingies require a bit of support to
> be included into the soft-core in order to run a real-time system, like
> a high precision timer and some stable monotonic clock source. Patrice
> Kadionik (the guy who lives there: http://uuu.enseirb.fr/~kadionik/)
> sent me an update for the FPGA design I used to do the initial port over
> nios2. This is mostly a matter of a couple of hours to fix and validate
> the I-pipe core accordingly, though.
Maybe you could ask for a hardware implementation of mul64by64_high...
>
> - powerpc32 updates for 2.6.30. Mainly to merge the once experimental
> bits that prevent most alignment faults from triggering a secondary mode
> switch. Andreas told me this works like a charm on 83xx, and I did not
> see any issue on 52xx, 85xx or 86xx either.
>
> - probably blackfin updates. I need to have a closer look, but I'm
> afraid I will have to resync with mainline before 2.5.0 is out. Blackfin
> folks never sleep it seems.
>
> - x86* updates to issue patches for the 2.6.30-stable and 2.6.31-stable
> series.
>
> You may have a few ARM patches brewing as well?
Actually yes. The "pic mute" feature was disabled on AT91 because it was
causing latency peaks, but I plan to enable it ultimately. I think the
latency peaks were due to the fact that I was testing a 2.4 with the bug
which we fixed in 2.4.9.1, I just need to check that. And if pic mute
works on AT91, then I would implement it for other SOCs. And an upgrade
to 2.6.31 would be fine too.
--
Gilles.
next prev parent reply other threads:[~2009-10-02 17:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 17:31 [Xenomai-core] RFC: 2.5 todo list Gilles Chanteperdrix
2009-09-30 14:10 ` Peter Soetens
2009-09-30 14:27 ` Gilles Chanteperdrix
2009-09-30 16:58 ` Peter Soetens
2009-09-30 19:04 ` Gilles Chanteperdrix
2009-09-30 14:56 ` Gilles Chanteperdrix
2009-10-01 7:06 ` Jan Kiszka
2009-09-30 22:44 ` Andreas Glatz
2009-10-01 11:32 ` Philippe Gerum
2009-10-02 16:21 ` Gilles Chanteperdrix
2009-10-02 17:41 ` Philippe Gerum
2009-10-02 17:48 ` Gilles Chanteperdrix [this message]
2009-10-02 19:18 ` Philippe Gerum
2009-10-02 19:59 ` Gilles Chanteperdrix
2009-10-02 20:09 ` Philippe Gerum
2009-10-02 20:20 ` Gilles Chanteperdrix
[not found] ` <4AC661D5.9090101@domain.hid>
2009-10-02 22:20 ` Philippe Gerum
2009-10-02 18:01 ` Andreas Glatz
2009-10-02 19:00 ` Philippe Gerum
2009-10-02 19:39 ` Wolfgang Denk
2009-10-02 19:45 ` Philippe Gerum
2009-10-06 18:26 ` Andreas Glatz
2009-10-06 19:55 ` Philippe Gerum
2009-10-06 20:10 ` Philippe Gerum
2009-10-15 19:21 ` Andreas Glatz
2009-10-20 16:35 ` Philippe Gerum
2009-10-21 14:32 ` Philippe Gerum
2009-10-21 14:48 ` Andreas Glatz
2009-10-07 15:40 ` Philippe Gerum
2009-10-02 19:25 ` Jan Kiszka
2009-10-02 19:52 ` Philippe Gerum
2009-10-02 20:19 ` Jan Kiszka
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=4AC63CF0.7090001@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=rpm@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.