From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Stephan Kappertz <stephan.kappertz@kabelmail.de>,
Paul <paul_c@tuxcnc.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: [Xenomai] Raspberry and Beaglebone patches
Date: Mon, 15 Apr 2013 08:57:45 +0200 [thread overview]
Message-ID: <516BA4E9.3070201@xenomai.org> (raw)
Hi Stephan, Paul,
we have a problem with the patches for Raspberry and BeagleBone: they
are based on the 3.2.21 patch, which we know is broken. So, we can not
really ship the next version of Xenomai with these patches.
There are two ways we could keep patches for these machines:
- you could send patches for 3.4 or 3.5, or even 3.8
- we could backport the fixes to 3.2, but as already discussed on this
list, this would cost some time to re-validate the 3.2 patch on all
architectures. However, if you do the backport, validate it on your
side, I could validate the result on my test boards, and we would
release a new version of the patch for 3.2 only for the ARM architecture.
Regards.
--
Gilles.
next reply other threads:[~2013-04-15 6:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 6:57 Gilles Chanteperdrix [this message]
2013-04-15 10:52 ` [Xenomai] Raspberry and Beaglebone patches Paul
2013-04-15 19:46 ` Gilles Chanteperdrix
2013-04-20 23:44 ` Paul
2013-04-21 0:01 ` Jason Kridner
2013-04-16 10:26 ` Stephan Kappertz
2013-04-16 18:06 ` Gilles Chanteperdrix
[not found] ` <F484004F-9908-449C-A4DA-CB73E47EE764@kabelmail.de>
[not found] ` <5182B1B5.1000107@xenomai.org>
2013-05-03 14:28 ` Stephan Kappertz
2013-05-03 18:19 ` Gilles Chanteperdrix
2013-05-03 20:41 ` Stephan Kappertz
2013-05-08 18:27 ` Gilles Chanteperdrix
2013-05-10 11:53 ` Stephan Kappertz
2013-05-10 13:21 ` Gilles Chanteperdrix
2013-05-10 14:43 ` Stephan Kappertz
2013-05-10 14:44 ` Gilles Chanteperdrix
2013-05-10 16:40 ` Stephan Kappertz
2013-05-10 16:48 ` Gilles Chanteperdrix
2013-05-10 17:02 ` Gilles Chanteperdrix
2013-05-13 10:37 ` Stephan Kappertz
2013-05-13 11:20 ` Stephan Kappertz
2013-05-14 6:41 ` Gilles Chanteperdrix
2013-05-14 6:50 ` Gilles Chanteperdrix
2013-05-14 7:33 ` Stephan Kappertz
2013-05-14 7:53 ` Gilles Chanteperdrix
2013-05-14 9:11 ` Stephan Kappertz
2013-05-14 9:20 ` Jan Kiszka
2013-05-14 9:44 ` Stephan Kappertz
2013-05-14 10:35 ` Jan Kiszka
2013-05-14 11:02 ` Gilles Chanteperdrix
2013-05-14 11:11 ` Jan Kiszka
2013-05-14 11:26 ` Gilles Chanteperdrix
2013-05-14 11:53 ` Jan Kiszka
2013-05-14 11:19 ` Stephan Kappertz
2013-05-14 11:26 ` Jan Kiszka
2013-05-14 18:30 ` Gilles Chanteperdrix
2013-05-15 7:34 ` Stephan Kappertz
2013-05-14 8:06 ` Stephan Kappertz
2013-05-13 11:22 ` Gilles Chanteperdrix
2013-05-13 11:52 ` Gilles Chanteperdrix
2013-05-13 22:49 ` Gilles Chanteperdrix
2013-05-18 15:04 ` 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=516BA4E9.3070201@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=paul_c@tuxcnc.org \
--cc=stephan.kappertz@kabelmail.de \
--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.