From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Didenko Sergey <didenkos@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] [Guide] To patch Linux Kernel with Xenomai for Unknown core
Date: Fri, 02 Oct 2009 19:15:34 +0200 [thread overview]
Message-ID: <4AC63536.2010802@domain.hid> (raw)
In-Reply-To: <1f3e02580910020652p7bc52284p7e26573669e1a05b@domain.hid>
Didenko Sergey wrote:
>>> For now on I have done with:
>>>
>>> - prepare kernel with adeos patch
>>> - configure kernel with its original defconfig file (the original
>>> configuration is verified and working fine on target board)
>>> - building kernel (and here we are!)
>>>
>>> 2) I did add implementation for (even though the I did not find any
>>> link to it in HOWTO, so I referred to PXA's implementation):
>>> __ipipe_check_tickdev (called from kernel\core.c)
>>>
>>> And for:
>>> mv88f6290_osmr0_set_mode
>>> mv88f6290_osmr0_set_next_event
>>> ckevt_mv88f6290_osmr0
>>> Even though all of them are required by __ipipe_mach_release_timer() I
>>> did not find in HOWTO how these functions should be implemented for
>>> MYCORE, so I referred to PXA's implementation again.
>
> *Gilles:*
> No, you should not add these functions. They already exist if your board
> supports GENERIC_CLOCKEVENT and GENERIC_TIME.
>
> *Sergey:*
> Unfortunately no, there is no these functions for my board, there are only
> for "arm\mach-pxa" and "arm\mach-sa1100".
Then your board does not support GENERIC_CLOCKEVENT and GENERIC_TIME,
and you should skip the section about it in the howto.
>
> *Q1: Does the fact that these options are enabled or disabled in kernel's
> .config file effects on how kernel code has been patched?*
> *
> *
> *Q2: Could anyone please explaine more exactly what do these options
> (GENERIC_CLOCKEVENT
> and GENERIC_TIME) mean? What are they doing and how? I realy want to
> understand it, but can not find any information about it.*
ask the internet.
http://lkml.indiana.edu/hypermail/linux/kernel/0701.2/1799.html
http://www.linuxworld.com/news/2007/022807-kernel.html
http://kernelnewbies.org/Linux_2_6_21#head-8547911895fda9cdff32a94771c8f5706d66bba0
http://lwn.net/Articles/223185/
--
Gilles.
next prev parent reply other threads:[~2009-10-02 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 10:43 [Xenomai-help] [Guide] To patch Linux Kernel with Xenomai for Unknown core Didenko Sergey
2009-09-30 11:53 ` Gilles Chanteperdrix
2009-10-02 13:52 ` Didenko Sergey
2009-10-02 17:15 ` Gilles Chanteperdrix [this message]
2009-10-03 1:55 ` Didenko Sergey
2009-10-03 7:21 ` 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=4AC63536.2010802@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=didenkos@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.