From: Michael Trimarchi <trimarchimichael@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] at91sam9260
Date: Sat, 15 Dec 2007 12:35:26 +0000 (GMT) [thread overview]
Message-ID: <136563.68019.qm@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
Hi,
>>
>> Hi,
>>
>> I think that the problem of the overruns are related to the latency
introduced by adeos, and the
>> serial buffer of the at91sam9260 ( length = 1 ).
>Wait a minute. You mean that you want more than 5000 interrupts by
>second ? Are you sure you do not get overruns with plain, unpatched
>Linux, if you load it sufficiently ?
Thank's for you help. I'm new on ipipe & xenomai. Yesterday I find a problem related to my patch and the at91 clock initialization ( I forgot to patch timex.h file ) and I will test serial line again as
soon as possible. Now I try to integrate the leatest patch of ipipe from the git repository.
I think that is not possible to have a "wired interrupt" for the root domain, or exclude ipipe
for a series of interrupt (just to try). I try to use linux without ipipe patch and I don't have
overrun on serial line. It is possible to count unhandled interrupt? Maybe I have some problem
but dosen't related to ipipe ( just visible with it ). are there test suite for ipipe?
Regards Michael
Regards Michael
___________________________________
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
http://it.docs.yahoo.com/nowyoucan.html
[-- Attachment #2: Type: text/html, Size: 1790 bytes --]
next reply other threads:[~2007-12-15 12:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 12:35 Michael Trimarchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-26 11:10 [Adeos-main] at91sam9260 Michael Trimarchi
2008-02-08 19:21 ` Bosko Radivojevic
2008-02-08 19:36 ` Gilles Chanteperdrix
2008-02-08 19:42 ` Bosko Radivojevic
2008-02-09 11:13 ` Michael Trimarchi
2008-02-09 13:39 ` Gilles Chanteperdrix
2007-12-20 18:44 Michael Trimarchi
2007-12-20 18:54 ` Gilles Chanteperdrix
2007-12-20 19:26 ` Gilles Chanteperdrix
2007-12-26 10:59 ` Gilles Chanteperdrix
2007-12-17 14:51 Michael Trimarchi
2007-12-17 14:20 Michael Trimarchi
2007-12-17 14:42 ` Gilles Chanteperdrix
2007-12-17 21:47 ` Gilles Chanteperdrix
2007-12-17 23:38 ` Gilles Chanteperdrix
2007-12-17 10:23 Michael Trimarchi
2007-12-17 10:26 ` Gilles Chanteperdrix
2007-12-17 14:11 ` Gilles Chanteperdrix
2007-12-15 13:06 Michael Trimarchi
2007-12-14 19:44 Michael Trimarchi
2007-12-14 20:15 ` Gilles Chanteperdrix
2007-12-13 15:41 Michael Trimarchi
2007-12-13 15:27 Michael Trimarchi
2007-12-13 15:32 ` Gilles Chanteperdrix
2007-12-15 11:59 ` Gilles Chanteperdrix
2007-12-11 18:33 Michael Trimarchi
2007-12-11 18:23 Michael Trimarchi
2007-12-11 18:24 ` Gilles Chanteperdrix
2007-12-11 17:19 Michael Trimarchi
2007-12-11 18:14 ` 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=136563.68019.qm@domain.hid \
--to=trimarchimichael@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@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.