From: Stefan Roese <stefan.roese@gmail.com>
To: mfornero@aanddtech.com
Cc: Xenomai@xenomai.org
Subject: Re: [Xenomai] Porting Ipipe to new ARM SoC (Xilinx Zynq)
Date: Mon, 14 Jan 2013 11:27:38 +0100 [thread overview]
Message-ID: <50F3DD9A.9050306@gmail.com> (raw)
In-Reply-To: <OF682F5C70.F8F7AA50-ON85257AF1.005F580A-85257AF1.005F580C@aanddtech.com>
Hi Matthew,
On 01/12/2013 06:21 PM, mfornero@aanddtech.com wrote:
> I'm looking for recommendations on how to best port ipipe support to a
> new ARM SoC. The SoC has started to show up in mainline, but many of
> the features haven't made it over yet. Xilinx maintains a git repo
> here:
>
> git://git.xilinx.com/linux-xlnx.git
>
> And it look like they've synced with mainline 3.6
>
> The two approaches I've considered were either trying to port ipipe to
> stock 3.6 (or at least the generic and ARM bits) or trying to backport
> the Xilinx code to 3.5.3. I started with the later approach, but some
> changes to the common clock architecture between 3.5 and 3.6 make this
> somewhat difficult.
>
> Any thoughts on which approach would be better?
I'm also working on supporting Zynq in I-pipe. My approach was to use
the Xilinx 3.5.0 code version (git tag "xilinx-14.3-build2"). And port
the I-pipe version from Gilles git repository to it. I still need to do
some cleanup then I can send you the latest version.
Best regards,
Stefan
next prev parent reply other threads:[~2013-01-14 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 17:21 [Xenomai] Porting Ipipe to new ARM SoC (Xilinx Zynq) mfornero
2013-01-14 10:27 ` Stefan Roese [this message]
2013-01-22 0:00 ` mfornero
2013-01-22 7:55 ` Gilles Chanteperdrix
2013-01-23 0:27 ` mfornero
2013-01-23 2:00 ` Gilles Chanteperdrix
2013-01-23 3:43 ` Matthew Fornero
2013-01-23 7:02 ` Gilles Chanteperdrix
2013-01-23 23:51 ` mfornero
2013-01-24 9:03 ` Gilles Chanteperdrix
2013-01-24 23:57 ` mfornero
2013-01-25 9:01 ` Gilles Chanteperdrix
[not found] ` <OFC84FDBBF.88E9186F-ON85257AFC.007B4CC3-85257AFC.008309FB@LocalDomain>
2013-01-24 0:12 ` mfornero
2013-02-10 14:23 ` Gilles Chanteperdrix
2013-02-13 17:57 ` mfornero
2013-02-13 18:14 ` Stefan Roese
2013-02-13 18:38 ` mfornero
2013-02-14 8:19 ` Stefan Roese
2013-02-13 19:44 ` Gilles Chanteperdrix
2013-02-14 19:41 ` Gilles Chanteperdrix
2013-02-14 19:42 ` 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=50F3DD9A.9050306@gmail.com \
--to=stefan.roese@gmail.com \
--cc=Xenomai@xenomai.org \
--cc=mfornero@aanddtech.com \
/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.