From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Michael Opdenacker" <michael@free-electrons.com>,
"Thomas Petazzoni" <thomas@free-electrons.com>,
"Boris Brezillon" <boris@free-electrons.com>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
xenomai@xenomai.org,
"Antoine Ténart" <antoine@free-electrons.com>
Subject: Re: [Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel
Date: Wed, 11 Jun 2014 20:16:15 +0200 [thread overview]
Message-ID: <53989CEF.3080205@xenomai.org> (raw)
In-Reply-To: <20140611092532.GE4254@lukather>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/11/2014 11:25 AM, Maxime Ripard wrote:
> On Tue, Jun 10, 2014 at 12:01:36PM +0200, Gilles Chanteperdrix
> wrote:
>> If you compile the kernel without I-pipe and Xenomai support and
>> enable the tcb_clksrc clocksource driver does it work?
>
> Yep, with the exact same config, except for CONFIG_IPIPE and
> CONFIG_XENOMAI being disabled, it boots fine.
>
Read again, I am not insterested in exactly the same config, I am
interested in the a config with tcb_clksrc clocksource, which is
disabled by CONFIG_IPIPE. Only if you enable this clocksource do you
get to use the atmel_tclib code.
Also, it would be nice if you could subscribe to the mailing list,
(and bounce all the messages you have sent so far to the mailing
list), so that mailing list users do not read only my answers.
Otherwise what you do is equivalent to using my personal e-mail
address for Xenomai questions, and usually, I do not answer such
questions.
- --
Gilles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iD8DBQFTmJzvGpcgE6m/fboRAtk8AJ9H4b3KDZJgQ57p0cHXHgs+oe4laQCeJ8nx
mTHbu4RuHYCDbUYkvevG0MY=
=9GGv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-06-11 18:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 13:59 [Xenomai] Xenomai on Atmel SAMA5D3 with a 3.14 kernel Maxime Ripard
2014-06-06 14:00 ` Maxime Ripard
2014-06-07 14:34 ` Gilles Chanteperdrix
2014-06-10 9:10 ` Maxime Ripard
2014-06-10 9:40 ` Maxime Ripard
2014-06-10 9:48 ` Gilles Chanteperdrix
2014-06-10 9:54 ` Maxime Ripard
2014-06-10 10:01 ` Gilles Chanteperdrix
2014-06-10 10:35 ` Gilles Chanteperdrix
2014-06-11 9:25 ` Maxime Ripard
2014-06-11 18:16 ` Gilles Chanteperdrix [this message]
2014-06-11 18:55 ` Gilles Chanteperdrix
2014-06-12 7:54 ` Maxime Ripard
2014-06-12 8:37 ` Gilles Chanteperdrix
2014-06-12 15:03 ` Maxime Ripard
2014-06-12 17:57 ` Gilles Chanteperdrix
2014-06-12 22:58 ` Gilles Chanteperdrix
2014-06-13 19:01 ` Gilles Chanteperdrix
2014-06-17 17:11 ` Maxime Ripard
2014-06-23 14:05 ` Maxime Ripard
2014-06-23 23:44 ` Gilles Chanteperdrix
2014-06-24 6:13 ` Gilles Chanteperdrix
2014-06-25 17:14 ` Maxime Ripard
2014-06-25 17:13 ` Maxime Ripard
2014-06-25 18:03 ` Gilles Chanteperdrix
2014-06-06 17:52 ` Gilles Chanteperdrix
[not found] ` <20140606180357.GE5594@piout.net>
2014-06-06 18:13 ` Gilles Chanteperdrix
2014-06-10 8:19 ` Maxime Ripard
2014-06-10 8:48 ` Gilles Chanteperdrix
2014-06-08 13:29 ` 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=53989CEF.3080205@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine@free-electrons.com \
--cc=boris@free-electrons.com \
--cc=maxime.ripard@free-electrons.com \
--cc=michael@free-electrons.com \
--cc=thomas@free-electrons.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.