All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Bob Feretich <bob.feretich@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Adeos patch interference with Angstrom 2.6.29-r46
Date: Tue, 06 Apr 2010 22:55:24 +0200	[thread overview]
Message-ID: <4BBB9FBC.5010400@domain.hid> (raw)
In-Reply-To: <4BBB9D96.7060808@domain.hid>

Bob Feretich wrote:
> Your statement concerns me. I need NEON/VFP support and here are four
> patches applied to it by the distribution.
>            file://vfp/02-vfp-ptrace.patch;patch=1 \
>            file://vfp/03-vfp-corruption.patch;patch=1 \
>            file://vfp/04-vfp-threads.patch;patch=1 \
>            file://vfp/05-vfp-signal-handlers.patch;patch=1 \
> Are these patches well known? Can you identify them from the above?

These URLs are relative to your system, I can not load the corresponding
file from this mail. But yes, these patches sound familiar to me and at
least some of then have been integrated in later versions of the Linux
kernel. The beagle board is supported by the mainline kernel, you have
no reason to use a distribution-specific fork.

Also note that the VFP support is broken in the Adeos I-pipe patch for
Linux 2.6.29. It has been fixed in the upcoming Adeos I-pipe patch for
Linux 2.6.31. Patch for 2.6.33, and maybe 2.6.32 should follow soon.


-- 
					    Gilles.


  reply	other threads:[~2010-04-06 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 21:22 [Xenomai-help] Adeos patch interference with Angstrom 2.6.29-r46 Bob Feretich
2010-04-05 22:18 ` Gilles Chanteperdrix
2010-04-06 20:46   ` Bob Feretich
2010-04-06 20:55     ` Gilles Chanteperdrix [this message]
2010-04-07  0:42       ` Bob Feretich
2010-04-08 12:16         ` 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=4BBB9FBC.5010400@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.