From: 梁权 <liang_1911@163.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re:Re: every millicsecond interrupt in xenomai domain on a am355x board can cause something wrong?
Date: Thu, 29 Nov 2018 23:58:11 +0800 (CST) [thread overview]
Message-ID: <26607a37.11532.1676031213b.Coremail.liang_1911@163.com> (raw)
In-Reply-To: <db92a4fc-b678-d86d-8a95-856369b87031@siemens.com>
i think it is hardly to run a vanilla 4.14.71 on that board , but i will try tomorrow.
it is 12 o'clock late at night in china; so i must go sleep now.thanks & good night guys
--
----------------------------------------------
梁权
THANKS & BR!
At 2018-11-29 23:25:30, "Jan Kiszka" <jan.kiszka@siemens.com> wrote:
>On 29.11.18 16:15, 梁权 wrote:
>> The linux 4.14.67 which i used is from the latest TI Linux Processor SDK for
>> AM335x; when i patch it with the /ipipe-core-4.14.71-arm-4.patch，/
>> i did not need to do any change except that telling where the file dmtimer.c is;
>> i guess it is because that in linux 4.14.67 the location of dmtimer.c is
>> different from which in linux 4.14.71
>>
>
>Could you try if you can reproduce the issue with vanilla 4.14.71 + I-pipe? Just
>to exclude downstream issues.
>
>I think there is no longer a need for a downstream kernel on that board, but I
>might be wrong (which would be sad).
>
>Jan
>
>--
>Siemens AG, Corporate Technology, CT RDA IOT SES-DE
>Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-29 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 8:03 every millicsecond interrupt in xenomai domain on a am355x board can cause something wrong? 梁权
2018-11-29 11:14 ` Jan Kiszka
2018-11-29 15:15 ` 梁权
2018-11-29 15:25 ` Jan Kiszka
2018-11-29 15:58 ` 梁权 [this message]
2018-11-29 14:34 ` Philippe Gerum
2018-11-29 15:27 ` 梁权
2018-11-29 15:39 ` Greg Gallagher
2018-11-29 15:50 ` 梁权
2018-11-29 16:40 ` Philippe Gerum
2018-11-30 16:44 ` 梁权
2018-12-02 7:07 ` 梁权
2018-12-02 10:00 ` Philippe Gerum
2018-12-05 4:17 ` 梁权
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=26607a37.11532.1676031213b.Coremail.liang_1911@163.com \
--to=liang_1911@163.com \
--cc=jan.kiszka@siemens.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.