All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Haberler <mail17@mah.priv.at>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Building BeagleBone kernel from git
Date: Wed, 21 Aug 2013 10:45:20 +0200	[thread overview]
Message-ID: <52147E20.3050500@siemens.com> (raw)
In-Reply-To: <A3E26082-0FC3-40D3-83B3-61D927953375@mah.priv.at>

On 2013-08-21 07:53, Michael Haberler wrote:
> 
> Am 20.08.2013 um 20:45 schrieb Sagar Behere <sagar.behere@gmail.com>:
> 
>> On 08/20/2013 08:39 PM, Gilles Chanteperdrix wrote:
>>> On 08/20/2013 04:58 PM, Charles Steinkuehler wrote:
>>>> I am currently working with LinuxCNC in a xenomai real-time environment
>>>> on the BeagleBone:
>>>>
>>>> http://bb-lcnc.blogspot.com/p/machinekit_16.html
>>>>
>>>> Everything is working well, but the kernel is being built using an
>>>> out-of-tree patch set obtained by Michael Haberler.
>>>>
>>>> I would like to switch to using a more 'official' xenomai build from
>>>> git, but am unclear how to proceed.
>>>>
>>>> Which git repository/branch would be the most appropriate for use in
>>>> building a xenomai kernel for the BeagleBone / AM335x SoC?
>>>>
>>>> Are there any 'gotchas' when using xenomai from git, or do the
>>>> instructions and procedures for using a released version apply?
>>>
>>> You can use kernel from the I-pipe git at:
>>> git://git.xenomai.org/ipipe.git branch ipipe-3.8
>>>
>>> And xenomai from the xenomai 2.6 git at:
>>> git://git.xenomai.org/xenomai-2.6.git branch master
>>>
>>> The only difference in the installation procedure when using this kernel
>>> with this version of Xenomai is that the "prepare-kernel.sh" script will
>>> not apply the I-pipe patch to the kernel, since the kernel is already
>>> patched, so the argument to the "--adeos" parameter of prepare-kernel.sh
>>> is ignored.
>>
>> For what it's worth, I tried this procedure and documented it
>>
>> https://github.com/sagarbehere/beaglebone-xenomai/blob/master/beaglebone-xenomai-debian.md
>>
> 
> Gilles says: use git://git.xenomai.org/ipipe.git branch ipipe-3.8
> Sagar uses git://git.xenomai.org/ipipe-jki.git origin/for-upstream/3.8

The official ipipe-3.8 is more recent than my upstream queue now, so the
former shall be used (specifically as I didn't test ARM back then).

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-08-21  8:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 14:58 [Xenomai] Building BeagleBone kernel from git Charles Steinkuehler
2013-08-20 18:39 ` Gilles Chanteperdrix
2013-08-20 18:45   ` Sagar Behere
2013-08-21  5:53     ` Michael Haberler
2013-08-21  8:45       ` Jan Kiszka [this message]
2013-08-20 19:49   ` Charles Steinkuehler
2013-08-20 19:55     ` Gilles Chanteperdrix
2013-08-20 20:25       ` Charles Steinkuehler
2013-08-20 22:37         ` Charles Steinkuehler
2013-08-20 23:12           ` Gilles Chanteperdrix
2013-08-21 22:15             ` [Xenomai] [PATCH] Fix for awk vs. gawk Charles Steinkuehler
2013-08-25 23:54               ` Gilles Chanteperdrix
2013-08-21 13:16         ` [Xenomai] Building BeagleBone kernel from git Charles Steinkuehler
2013-08-21 18:25           ` Gilles Chanteperdrix
2013-08-24 17:10             ` Ralf Roesch
2013-08-24 17:54               ` Michael Haberler
2013-08-25  0:59               ` Charles Steinkuehler
2013-08-25  7:24                 ` Ralf Roesch
2013-08-27 19:59             ` [Xenomai] [PATCH] BeagleBone 3.8.13 pre/post patches Charles Steinkuehler
2013-08-27 21:12               ` Gilles Chanteperdrix
2013-08-27 21:13                 ` Gilles Chanteperdrix
2013-08-27 21:57                   ` Charles Steinkuehler
2013-09-10 18:48               ` Gilles Chanteperdrix
2013-09-10 21:20                 ` Charles Steinkuehler

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=52147E20.3050500@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=mail17@mah.priv.at \
    --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.