From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Iker Amescua <iamescua@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Adeos I-PIPE NS9215 port problem
Date: Fri, 02 Jul 2010 13:39:51 +0200 [thread overview]
Message-ID: <4C2DD007.4090300@domain.hid> (raw)
In-Reply-To: <1278069874.8669.25.camel@domain.hid>
Iker Amescua wrote:
>
> Changing to handle_ir_level make the system boot a bit further, but
> still locks.
>
> In the ns921x_timer_init function there is a call to to
> clocksource_register(&ns921x_clocksource) and it is configured (timer 0)
> in enabled mode REGSET(tc, SYS_TCx, TE, EN), up counter, 32 bits
> autoreload, so I think this is the clocksource. I attach full
> time-ns921x.c (I hope I haven't missed anything).
Yes, you register the clocksource and clockevents, but that does not
make the Linux kernel use them. If it has other clocksources, it may
decide to use them. Or maybe the clockevents support is not even
compiled because the GENERIC_CLOCKEVENTS and GENERIC_CLOCKSOURCE are not
in your kernel configuration.
Anyway, you should do things step by step:
- run the I-pipe patch alone, without Xenomai
- try and get the kernel booting, find where it is stuck, (I would say
probably somewhere in the handling of interrupts, if that is the case,
you need to check some doc about how your interrupt controller works,
how the EOI works, etc...)
- when it boots, try cat /proc/timer_list and see what is the status of
clockevents/clocksource, try to get it to use the clocksource and
clockevents you implemented.
- enable Xenomai.
--
Gilles.
prev parent reply other threads:[~2010-07-02 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 8:58 [Adeos-main] Adeos I-PIPE NS9215 port problem Iker Amescua
2010-07-02 9:20 ` Gilles Chanteperdrix
2010-07-02 10:24 ` Iker Amescua
2010-07-02 10:59 ` Gilles Chanteperdrix
2010-07-02 11:15 ` Gilles Chanteperdrix
2010-07-02 11:24 ` Iker Amescua
2010-07-02 11:39 ` Gilles Chanteperdrix [this message]
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=4C2DD007.4090300@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=iamescua@domain.hid \
/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.