From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>,
Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [announce] Xenomai 2.5.6
Date: Tue, 08 Mar 2011 19:05:40 +0100 [thread overview]
Message-ID: <4D766FF4.20503@domain.hid> (raw)
In-Reply-To: <4D766E9E.6050207@domain.hid>
Wolfgang Grandegger wrote:
> Hi Gilles,
>
> On 03/08/2011 02:01 PM, Gilles Chanteperdrix wrote:
>> Hi,
>>
>> Xenomai 2.5.6, a.k.a. "Wormhole Wizards" is available at the usual
>> place:
>> http://download.gna.org/xenomai/stable/xenomai-2.5.6.tar.bz2
>>
>> It contains mainly bug fixes, for:
>> - SMP scheduling bugs introduced by the "optimization" in the last
>> release;
>> - a cleanup of all architectures kernel threads initializations,
>> triggered by an issue on powerpc;
>> - some psos skin updates;
>> - some analogy updates;
>> - some compilation issues on ARM and x86 for latest toolchains, and with
>> uclibc;
>> - some issues with gdb on blackfin.
>>
>> And as usual an update of many I-pipe patches, including modifications
>> to use the latest kernel release to date (2.6.37), and wrappers fixes.
>
> Thanks a lot. I'm looking to the new ARM patches:
>
> adeos-ipipe-2.6.33-arm-1.18-02.patch
> adeos-ipipe-2.6.35.9-arm-1.18-01.patch
>
> Why is ipipe version 1.18-01 used for 2.6.35.9 (and not 1.18-02)? Or is
> it just a typo?
Just because 2.6.35.9-1.18-01 was made from 2.6.33-1.18-01, then 2.6.33
was improved, and triggered a new release. There is no reason really.
Maybe calling 2.6.35.9-1.18-00 would have made more sense.
--
Gilles.
next prev parent reply other threads:[~2011-03-08 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:01 [Xenomai-core] [announce] Xenomai 2.5.6 Gilles Chanteperdrix
2011-03-08 17:59 ` Wolfgang Grandegger
2011-03-08 18:05 ` Gilles Chanteperdrix [this message]
2011-03-08 21:45 ` [Xenomai-help] " Lin Zhang
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=4D766FF4.20503@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
--cc=wg@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.