Am Samstag, den 15.12.2012, 13:04 +0100 schrieb Gilles Chanteperdrix: > The latest Adeos is the core-3.4 branch from the git.denx.de/ipipe.git > repository, not the 'for-core-3.4' branch from the > git.xenomai.org/ipipe-gch.git. Ah, thanks for clearing up.
> Anyway, you can not use Xenomai 2.6.1 with linux 3.4, you also have to > use xenomai from its git repository git.xenomai.og/xenomai-2.6.git It's working here fine. Why do you expect, that Xenomai 2.6.1 and linux 3.4 won't work together? I'm using 'for-core-3.4' branch from git.xenomai.org/ipipe-gch.git with Linux 3.4.14. I just build a big diff from 'for-core-3.4' against 3.4.6 and applied this on my 3.4.14. Then i took all the kernel-src files and Kconfig changes from xenomai-2.6.1.tar.bz2 and build again a patch. I use simple patches as they are easier for me to maintain in ptxdist. > > While hunting a gpio-irq latency i tried to understand the adeos chained > > How high a latency are we talking about? The latency was about ~11µs. I then found out, that the cpu clock wasn't the full 600MHz. I changed this and now the gpio-irq latency is about ~7µs. In contrast, the timer-irq latency is less than 3µs. But when i use IPIPE_IRQF_NOSYNC the gpio-irq latency rises to ~14µs. But on the other hand the switch between gpio-irq and timer-irq is faster with IRQF_NOSYNC. It takes ~3µs and without IRQF_NOSYNC is takes ~7µs. > Anyway, the way we track down this kind of issues is the I-pipe tracer. > http://www.xenomai.org/index.php/I-pipe:Tracer > > You will have to trigger the freeze yourself if you find a too high latency. It's a great tool. I played a bit with the tracer, but 11µs is very short, so it's difficult. -- Tim Niemeyer Corscience GmbH & Co. KG Henkestr. 91 D-91052 Erlangen Germany e-mail: [email protected] Internet: www.corscience.de _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
