From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Henri Roosen <henriroosen@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Read TSC results in bus error (ARM iMX25)
Date: Wed, 28 Oct 2009 17:42:51 +0100 [thread overview]
Message-ID: <4AE8748B.3070706@domain.hid> (raw)
In-Reply-To: <b88603c30910280917x1eaa89f2q26c7283e381d05f1@domain.hid>
Henri Roosen wrote:
> This code is part of the iMX25 bsp that is not part of any kernel yet,
> so generating a patch is not possible. Seems the upcoming 2.6.32
> kernel will have support for iMX25, but the -rc5 still has
> build-failures for this platform.
Ok. But could you point me to the code in the mach-mx3 tree? I do not
find any cpu.c. The Denx Qong box probably has the same issue as imx25,
and I would be interested in fixing it.
>
> Maybe the complete BSP with ipipe for the iMX25 and 2.6.28 kernel
> might be interesting for release (similar as the patch
> ipipe-2.6.26-mxc.diff), but is still in an early development state:
> now the latency app runs I see it runs fine only for a few minutes and
> then gets overruns... asks for debugging ;-)
Ok. You can try and use the I-pipe tracer. And make sure to run latency
-p 1000. I can have a look at your I-pipe code to see if I do not see
anything obvious.
--
Gilles
next prev parent reply other threads:[~2009-10-28 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 14:34 [Xenomai-help] Read TSC results in bus error (ARM iMX25) Henri Roosen
2009-10-28 14:45 ` Gilles Chanteperdrix
[not found] ` <b88603c30910280753uea312e1p3d5f62012814d355@domain.hid>
[not found] ` <4AE860FB.4090903@domain.hid>
2009-10-28 15:25 ` Henri Roosen
2009-10-28 15:28 ` Gilles Chanteperdrix
2009-10-28 16:17 ` Henri Roosen
2009-10-28 16:42 ` Gilles Chanteperdrix [this message]
2009-10-28 17:34 ` Henri Roosen
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=4AE8748B.3070706@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=henriroosen@domain.hid \
--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.