All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitchell Tasman <tasman@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Arm support for 3.2 kernel?
Date: Mon, 09 Jan 2012 20:13:42 -0500	[thread overview]
Message-ID: <4F0B90C6.8040007@domain.hid> (raw)

Hi.  I saw the recent discussion regarding ARM I-pipe and 3.x, and am 
wondering if anyone can hazard a guess as to a timetable for 3.2 support?

For OMAP3, I've wondered what's considered the optimal kernel strategy: 
mainline, linux-omap, or an OMAPPSP branch of TI's linux-omap3 staging 
tree on Arago.  My understanding based on previous discussions is that 
for anything but mainline, a Xenomai user is on his or her own as far as 
adapting an ARM I-pipe patchset to the selected kernel.  And for 
mainline, one risks incomplete or incorrect OMAP3 support.  I presume 
that newer mainline kernel versions contain more complete/correct OMAP3 
support than do older ones; hence, my question about 3.2.

Thanks.


             reply	other threads:[~2012-01-10  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  1:13 Mitchell Tasman [this message]
2012-01-10 20:14 ` [Xenomai-help] Arm support for 3.2 kernel? Gilles Chanteperdrix
2012-01-19  0:26   ` Mitchell Tasman
2012-01-19 14:53     ` babbittner
2012-01-19 16:43       ` Terry Fryar
2012-01-21 18:03         ` Josh Karch

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=4F0B90C6.8040007@domain.hid \
    --to=tasman@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.