From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: WONG Sheng Chao <wong@isir.upmc.fr>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Compiling I-pipe patched kernel on beaglebone from Angstrom branch
Date: Mon, 10 Dec 2012 21:32:50 +0100 [thread overview]
Message-ID: <50C646F2.9040904@xenomai.org> (raw)
In-Reply-To: <ebaafe297f9d50512d32831f8757cb3b@isir.upmc.fr>
On 12/10/2012 09:23 PM, WONG Sheng Chao wrote:
> I'm sorry but can you be more specific about the error i made as i am
> still new to source control. What do you mean by putting xenomai in the
> sources? What i did was
>
> 1) Pre patch the vendor source to remove the conflict files for ipipe
> patch
>
> 2) Patch the updated vendor source with ipipe using prepare-kernel.sh (
> Is this a mistake? )
Yes. And the pre and post patch can be generated from a working tree,
they are not what you should put under version control.
>
> 3) post patch the ipipe patched source
>
> 4) Compile and deploy the kernel
You should run prepare-kernel.sh at this point, using the I-pipe patched
kernel, and keep the I-pipe patched kernel and xenomai sources separate,
so that you can update them separately.
--
Gilles.
next prev parent reply other threads:[~2012-12-10 20:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1354186801.18650.xenomai@xenomai.org>
2012-11-29 12:16 ` [Xenomai] Compiling I-pipe patched kernel on beaglebone from Angstrom branch Stephan Kappertz
2012-11-30 8:54 ` WONG Sheng Chao
2012-11-30 11:45 ` Michael Haberler
2012-11-30 13:42 ` Gilles Chanteperdrix
2012-11-30 19:22 ` Michael Haberler
2012-12-02 13:53 ` WONG Sheng Chao
2012-12-02 14:45 ` Gilles Chanteperdrix
2012-12-02 15:15 ` WONG Sheng Chao
2012-12-02 16:14 ` Gilles Chanteperdrix
2012-12-03 14:31 ` WONG Sheng Chao
2012-12-03 18:30 ` WONG Sheng Chao
2012-12-03 19:57 ` Gilles Chanteperdrix
2012-12-04 9:26 ` WONG Sheng Chao
2012-12-04 9:45 ` WONG Sheng Chao
2012-12-04 19:29 ` Gilles Chanteperdrix
2012-12-10 18:08 ` WONG Sheng Chao
2012-12-10 19:07 ` Gilles Chanteperdrix
2012-12-10 20:23 ` WONG Sheng Chao
2012-12-10 20:32 ` Gilles Chanteperdrix [this message]
[not found] <mailman.2.1354034873.1423.xenomai@xenomai.org>
2012-11-27 18:42 ` Stephan Kappertz
2012-11-27 20:05 ` WONG Sheng Chao
2012-11-23 9:45 WONG Sheng Chao
2012-11-23 9:58 ` Gilles Chanteperdrix
2012-11-23 12:35 ` WONG Sheng Chao
2012-11-23 16:29 ` Gilles Chanteperdrix
2012-11-23 17:22 ` WONG Sheng Chao
2012-11-23 17:45 ` Gilles Chanteperdrix
2012-11-27 16:40 ` WONG Sheng Chao
2012-11-27 16:52 ` WONG Sheng Chao
2012-11-27 18:00 ` Gilles Chanteperdrix
2012-11-28 15:12 ` WONG Sheng Chao
2012-11-28 17:40 ` WONG Sheng Chao
2012-11-28 18:14 ` Gilles Chanteperdrix
2012-11-28 18:49 ` WONG Sheng Chao
2012-11-28 18:57 ` Gilles Chanteperdrix
2012-11-28 19:34 ` WONG Sheng Chao
2012-11-28 19:55 ` Gilles Chanteperdrix
2012-11-28 20:22 ` WONG Sheng Chao
2012-11-29 12:10 ` WONG Sheng Chao
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=50C646F2.9040904@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=wong@isir.upmc.fr \
--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.