From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: GP Orcullo <kinsamanka@gmail.com>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] [PATCH] Add support for SUNXI boards
Date: Thu, 16 Apr 2015 18:43:10 +0200 [thread overview]
Message-ID: <20150416164310.GH1589@hermes.click-hack.org> (raw)
In-Reply-To: <552FE54F.6090606@siemens.com>
On Thu, Apr 16, 2015 at 06:37:35PM +0200, Jan Kiszka wrote:
> On 2015-04-16 18:16, Gilles Chanteperdrix wrote:
> > On Fri, Apr 17, 2015 at 12:04:22AM +0800, GP Orcullo wrote:
> >> On Thu, Apr 16, 2015 at 9:19 PM, Gilles Chanteperdrix
> >> <gilles.chanteperdrix@xenomai.org> wrote:
> >>> On Thu, Apr 16, 2015 at 04:05:05PM +0800, GP Orcullo wrote:
> >>>> Tested on a Cubieboard2 with v3.16.7-ckt9 kernel.
> >>>
> >>> Does not sunxi have GPIO ?
> >>>
> >>> --
> >>> Gilles.
> >>
> >> There's no GPIO driver in the mainline kernel. The original sunxi
> >> kernel has incomplete support for GPIOs.
> >
> > Ok, what about timer and tsc? Basically, you should run through the
> > ARM porting guide and check every modification to be made. And if
> > you have done so, the commit message should mention it.
>
> sunxi is pretty generic ARMv7-class in that regard, but double-checking
> is surely better.
armv7 does not mean a particular timer. Cortex A9 or cortex A15 do,
but different ones, and Cortex A8 does not for instance. The
processor we are talking about is probably not a cortex A9 since on
I-pipe, there is no timer or tsc defined on A9 when booting in UP
mode (and GP Orcullo is booting in UP mode). So my question is not
about "double-checking", it is rather the first check.
>
> If time permits, I will give things a try on our Banana Pi - provided it
> is fine with such an old kernel (I only started with 3.19 on it).
--
Gilles.
next prev parent reply other threads:[~2015-04-16 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 8:05 [Xenomai] [PATCH] Add support for SUNXI boards GP Orcullo
2015-04-16 13:19 ` Gilles Chanteperdrix
2015-04-16 16:04 ` GP Orcullo
2015-04-16 16:16 ` Gilles Chanteperdrix
2015-04-16 16:37 ` Jan Kiszka
2015-04-16 16:43 ` Gilles Chanteperdrix [this message]
2015-04-16 16:53 ` Jan Kiszka
2015-04-16 16:56 ` Gilles Chanteperdrix
2015-04-18 6:56 ` Maxime Ripard
2015-04-18 9:34 ` Jan Kiszka
2015-04-18 11:50 ` Maxime Ripard
2015-04-16 22:29 ` GP Orcullo
2015-04-16 23:13 ` Gilles Chanteperdrix
2015-04-18 6:55 ` Maxime Ripard
2015-04-18 8:05 ` GP Orcullo
2015-04-18 8:16 ` Maxime Ripard
2015-04-18 14:45 ` GP Orcullo
2015-04-18 15:20 ` 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=20150416164310.GH1589@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=kinsamanka@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.