From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Bob Feretich <bob.feretich@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Interpreting the ksrc/arch/arm/patches directory
Date: Wed, 24 Feb 2010 15:05:57 +0100 [thread overview]
Message-ID: <4B853245.3080603@domain.hid> (raw)
In-Reply-To: <4B8445C0.2010101@domain.hid>
Bob Feretich wrote:
> The ksrc/arch/arm/patches directory for xenomai-2.5.git shows entries
> for Linux 2.6.28.10, 2.6.29, and 2.6.30 kernels. The release news for
> xenomai-2.5.1 states that its "preparing support for the upcoming 2.6.33
> kernel", implying that 2.6.32 is the latest kernel supported.
>
> Am I correct as interpreting this to mean xenomai-2.5.1 supports 2.6.32
> on some architectures, but for the arm architecture 2.6.30 is the latest
> supported level?
Yes, ARM support lags behind. I need to work on that. We will probably
skip 2.6.31 et go to 2.6.32 directly.
>
> Also the patches README file doesn't list the BeagleBoard as being
> supported, however other news states that BeagleBoard support was added
> in xenomai-2.5. Is BeagleBoard support still in xenomai-2.5.1?
The beagle is supported. That is a mistake in the README, and in fact,
the README should not mention any board name at all, because this is the
kind of file we always forget.
>
> Regards,
> Bob
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
--
Gilles.
next prev parent reply other threads:[~2010-02-24 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:16 [Xenomai-help] Interpreting the ksrc/arch/arm/patches directory Bob Feretich
2010-02-24 7:24 ` Philippe Gerum
2010-02-24 14:05 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-24 18:07 Bob Feretich
2010-02-24 20:07 ` 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=4B853245.3080603@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=bob.feretich@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.