From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: mfornero@aanddtech.com
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] (no subject)
Date: Sat, 23 Mar 2013 17:15:01 +0100 [thread overview]
Message-ID: <514DD505.2040306@xenomai.org> (raw)
In-Reply-To: <OFFC519FEC.3D6ECA30-ON85257B37.00588608-85257B37.0058860B@aanddtech.com>
On 03/23/2013 05:06 PM, mfornero@aanddtech.com wrote:
>>> Is there a new ADEOS patch for ARM in the works ? I am interested to know
>>> what kernel version is targeted if that decision has been made.
>
>> 3.8. It currently works on at91s, but not yet on omap. We will probably
>> need to run tests on the imxs, as a lot of things have changed between
>> 3.5 and 3.8.
>
> Hi Gilles,
Hi,
your mail agent is not correctly configured, it sent the mail with an
empty suject, and without the "In-Reply-To, or References" headers set.
Please fix this. Your lines are also too long.
>
> Is there a public git tree with this work-in-progress? I couldn't pinpoint a
> specific one on git.xenomai.org or git.denx.de that was ARM/3.8 based
It is ipipe-gch.git, but the work in progress is not currently pushed
there, because I need to be able to rebase.
>
> The Xilinx -next tree for Zynq looks like it's based on 3.8, so a 3.8 ipipe would
> likely be much easier for me than attempting to back port all of the important patches.
>
> On a related note, is there something I can do to help prevent the Zynq ipipe port from
> bit-rotting? Even in 3.8, mainline is still missing a lot of the necessary code for Zynq,
> so I assume I'd need a pre- and post- patch. Could you elaborate on what these would entail?
The pre- and post- patches allow a SOC-specific port on a vendor branch
to only contain SOC-specific changes, and not the core of the I-pipe
changes, allowing to update the I-pipe patch without updating the
SOC-specifc port. The pre and post patches are artificial, generated
with differences between specific trees, they do not need to reflect the
way you maintaint the SOC-specific I-pipe for the vendor branch.
Regards.
--
Gilles.
next prev parent reply other threads:[~2013-03-23 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 16:06 [Xenomai] (no subject) mfornero
2013-03-23 16:15 ` Gilles Chanteperdrix [this message]
2013-03-24 22:52 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2017-12-17 16:49 rajae rajae
2017-12-17 17:23 ` Greg Gallagher
2017-08-29 9:09 Xu Chen
2015-11-25 16:45 Umair Ali
2015-08-19 11:58 Mohamed Fawzy
2015-08-21 9:18 ` Nicolas SCHURANDO
2015-08-21 9:26 ` Gilles Chanteperdrix
2015-03-30 14:51 Helder Daniel
2014-05-01 23:58 alex.martin92
2013-07-22 7:27 Franz Engel
2013-03-27 16:23 Mohammadreza Babaee
2013-03-27 20:51 ` Gilles Chanteperdrix
2013-01-26 9:44 Amit Bhaira
2013-01-27 15:31 ` Gilles Chanteperdrix
2013-01-04 14:37 RAGHAVENDRA GANIGA
2012-12-15 8:49 Shamju Joseph
2012-12-15 11:50 ` 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=514DD505.2040306@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=mfornero@aanddtech.com \
--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.