From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Fredrik Asplund <fasplund@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai and Gumstix Overo
Date: Wed, 30 Jun 2010 10:28:51 +0200 [thread overview]
Message-ID: <4C2B0043.1070108@domain.hid> (raw)
In-Reply-To: <22150A2C94CC924695BE248F94CD11F2CDC2@domain.hid>
Fredrik Asplund wrote:
>> Xenomai 2.5.3 was tested on OMAP3 with the mainline kernel. If you
>> absolutely want to use this vendor branch, you will have to fix the
>> patch rejects by hand.
>
> Ok, yes, I thought so. I guess I was hoping someone had done the same
> thing and had some pointers on what to do in this specific case (i.e.
> applying Xenomai using Bitbake on a vendor branch).
>
> I will try to apply the patch rejects (I want to deviate from the
> original setup as little as possible, at least to begin with)
If you do not want to deviate from Xenomai usual setup, use the mainline
kernel. If I were you, I would have serious doubts on a vendor kernel
which touches generic files such as include/asm/cacheflush.h in order to
add some board-specific code.
, but
> when I went through the source folder I couldn´t find any "*.rej"
> files (even though the log suggests they were created). Do I need to
> call the prepare-kernel.sh script differently somehow or is the
> problem in my tool environment?
The log is the result of running patch in "dry-run" mode, so that if it
fails, prepare-kernel.sh does not break your sources. Apply the adeos
patch by hand with the patch command. Once the sources are fixed,
prepare-kernel.sh will be able to detect that your kernel is already
patched and will skip that step.
>
> / Fredrik
--
Gilles.
next prev parent reply other threads:[~2010-06-30 8:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 19:40 [Xenomai-help] Xenomai and Gumstix Overo Fredrik Asplund
2010-06-29 20:03 ` Gilles Chanteperdrix
2010-06-30 8:17 ` Fredrik Asplund
2010-06-30 8:28 ` Gilles Chanteperdrix [this message]
2010-06-30 21:58 ` Felipe Brandão Cavalcanti
2010-07-01 3:01 ` Thomas Lockhart
2010-07-01 6:49 ` Gilles Chanteperdrix
2010-07-01 7:17 ` Gilles Chanteperdrix
2010-07-01 8:11 ` Fredrik Asplund
2010-07-01 8:59 ` Fredrik Asplund
2010-07-01 9:54 ` Gilles Chanteperdrix
2010-07-01 10:16 ` Fredrik Asplund
2010-07-01 12:22 ` Fredrik Asplund
2010-07-01 23:25 ` Felipe Brandão Cavalcanti
2010-07-02 7:33 ` Fredrik Asplund
2010-07-02 12:29 ` Fredrik Asplund
2010-07-02 12:35 ` Felipe Brandão Cavalcanti
2010-07-02 12:40 ` Gilles Chanteperdrix
2010-07-02 12:45 ` Fredrik Asplund
2010-07-02 12:59 ` Felipe Brandão Cavalcanti
2010-07-03 9:07 ` Fredrik Asplund
2010-07-03 19:53 ` Felipe Brandão Cavalcanti
2010-07-05 7:44 ` Fredrik Asplund
2010-07-05 13:13 ` Felipe Brandão Cavalcanti
2010-07-05 13:21 ` Fredrik Asplund
2010-07-05 13:34 ` Fredrik Asplund
2010-07-05 20:15 ` Felipe Brandão Cavalcanti
2010-07-03 20:04 ` Gilles Chanteperdrix
2010-07-05 7:52 ` Fredrik Asplund
2010-07-02 8:14 ` Gilles Chanteperdrix
2010-07-02 12:34 ` Felipe Brandão Cavalcanti
2010-07-02 12:39 ` 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=4C2B0043.1070108@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=fasplund@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.