From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: uMinded Strikes Again <iceblu3710@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Fwd: Porting IPIPE to SUN5I (Allwinner A13)
Date: Wed, 13 Feb 2013 22:09:35 +0100 [thread overview]
Message-ID: <511C010F.4030304@xenomai.org> (raw)
In-Reply-To: <CAPeEharzL54WkK2TCBmQo7ec8Aa1-t1dyBKuHBeZ0hLzGgCiwQ@mail.gmail.com>
On 02/13/2013 09:30 PM, uMinded Strikes Again wrote:
> Ok so I am on my way with kernel version 3.4.29 however my sun5i directory
> is quite lacking. If I compare /arch/arm/omap2/ their are dozens of files
> to the SOC features and a complete Kconfig file as well but in my
> /arch/arm/sun5i/ their are just the basics for the clock to run and no
> Kconfig at all!
>
> Is their a drivers patch out there for the sunxi chipsets or will I be
> writing my own for this whole architecture??
If you have a support for the 3.0 kernel, you may adapt it to a newer
kernel. Or indeed use the 3.0 kernel as a base for Xenomai. In this
case, the guide is:
http://xenomai.org/index.php/I-pipe:ArmPorting
Is what we have to help you. But:
- it seems the I-pipe core patches are a bit easier to port to new ARM
boards (we already had 3 new ports since the first I-pipe core patch for
3.2);
- this document is quite outdated, you would have to use the new version
explanations about GPIOs demuxing or tsc emulation;
- getting the full support for the processor you are intereseted in
merged into the mainline kernel may be more future proof than getting
stuck with Linux 3.0.
--
Gilles.
prev parent reply other threads:[~2013-02-13 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 4:08 [Xenomai] Porting IPIPE to SUN5I (Allwinner A13) uMinded Strikes Again
2013-02-13 8:40 ` Gilles Chanteperdrix
[not found] ` <CAPeEhaq-oMmhntc3rYDt-e1=qEorjkVj8G+qYKcNSxOggjGH7A@mail.gmail.com>
2013-02-13 20:30 ` [Xenomai] Fwd: " uMinded Strikes Again
2013-02-13 21:09 ` Gilles Chanteperdrix [this message]
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=511C010F.4030304@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=iceblu3710@gmail.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.