From: Edward Hoffman <quantalgo@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Alexis Berlemont <berlemont.hauw@domain.hid>,
Xenomai core <Xenomai-core@domain.hid>,
Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] (Not yet) Xenomai 2.5.5.
Date: Thu, 16 Sep 2010 12:50:46 -0400 [thread overview]
Message-ID: <1284655846.7155.1.camel@domain.hid> (raw)
In-Reply-To: <4C91E05E.6010202@domain.hid>
Jan,
Sorry, I got distracted with the rtnet testing and development I'll be
back on the 32-bit version early next week.
Ed
On Thu, 2010-09-16 at 11:16 +0200, Jan Kiszka wrote:
> Am 16.09.2010 10:17, Gilles Chanteperdrix wrote:
> >
> > Hi,
> >
> > I would like to make that next release of Xenomai, especially since the
> > fix for the I-pipe on x86_32 with grub2 has been available for some time
> > now, and has not yet been in a stable release.
> >
> > So, I have a few minor questions:
> > - Wolfgang, Alexis, it seems we have a few warnings when compiling
> > rtcan/analogy tools with recent versions of gcc (4.4.1 from
> > codesourcery). You will find the logs here:
> > http://sisyphus.hd.free.fr/~gilles/pastebin/KVSBtb
> > we are not in a hurry to fix this, so simply tell me if the fix is easy
> > or not.
> > - Alexis, from the mailing list discussions, you probably have some
> > commits ready in the analoty branch, would it be possible to have a pull
> > request for these?
> > - Jan, where are we with CLOCK_HOST_REALTIME, are the I-pipe ready?
> > Should I merge Wolfgang's patches, or the I-pipe/Xenomai interface has
> > changed following the discussions with Philippe?
>
> I've a ready-to-use version that should address all of Philippe's
> remarks in my 2.6.35 queue [1]. The plan was to push it along this line,
> but then things got stuck due to the 32-bit boot hang report by Ed
> Hoffman (still waiting for further information from him). Also my KVM
> patches in that queue do not work yet, but they will likely be postponed.
>
> Besides that, I've longer queue of fixes and enhancement to Xenomai [2]
> that partially depends on [1]. I already sent pull requests, but then
> did not refresh it due to the dependency.
>
> Unfortunately, I'm "a bit" short on time the next weeks, so we need to
> find the cheapest way of getting the most important stuff merged for
> 2.5.5 I guess. I already started backporting the critical sync fixes for
> I-pipe to 2.6.34 [3], just sent no pull request yet.
>
> Jan
>
> [1]
> http://git.kiszka.org/?p=ipipe-2.6.git;a=shortlog;h=refs/heads/queues/2.6.35-x86
> [2]
> http://git.xenomai.org/?p=xenomai-jki.git;a=shortlog;h=refs/heads/for-upstream
> [3]
> http://git.kiszka.org/?p=ipipe-2.6.git;a=shortlog;h=refs/heads/queues/2.6.34-x86
>
next prev parent reply other threads:[~2010-09-16 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 8:17 [Xenomai-core] (Not yet) Xenomai 2.5.5 Gilles Chanteperdrix
2010-09-16 9:16 ` Jan Kiszka
2010-09-16 16:50 ` Edward Hoffman [this message]
2010-09-16 18:51 ` Gilles Chanteperdrix
2010-09-16 23:35 ` Jan Kiszka
2010-09-16 23:41 ` Gilles Chanteperdrix
2010-09-17 10:11 ` Gilles Chanteperdrix
2010-09-16 12:13 ` [Xenomai-help] " Stefan Kisdaroczi
2010-09-16 18:44 ` [Xenomai-core] " Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2010-09-19 3:55 Edward Hoffman
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=1284655846.7155.1.camel@domain.hid \
--to=quantalgo@domain.hid \
--cc=Xenomai-core@domain.hid \
--cc=berlemont.hauw@domain.hid \
--cc=jan.kiszka@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.