All of lore.kernel.org
 help / color / mirror / Atom feed
From: Flavio Castro Alves Filho <flavio.alves@gmail.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Beaglebone kernels - automated builds WIP
Date: Sat, 8 Jun 2013 19:46:40 -0300	[thread overview]
Message-ID: <CAFNBftcwKG_t_wEOwHaE850UCo7aHprtpf2HU83_H0MKH71p-Q@mail.gmail.com> (raw)
In-Reply-To: <CAFNBfteWESjgYQeMH0kv2w3qVGuX+XUkWqCNhbYPimH+vLcGTA@mail.gmail.com>

Answering my own question:

=> My setup

Ubuntu 12.04 with a complete build of Angstrom for BeagleBone Black
using openembedded setup scripts

I used 'bitbake meta-ide-support' in order to have the toolchain for
building the kernel.

Despite having the build system, I'm using the original image from
e-mmc without changing anything

=> My procedure

* I used ipipe.git repository and ipipe-next branch as my mainline
kernel source code. I assumed that it was equivalent to the mainline
kernel with the v3.8.10 tag with the additions of the adeos-ipipe
equivalent patches (if we use the Xenomai's installer from the
download package)
* I added the BeagleBone Black related patches. To do so, I got the
meta-beagleboard from Yocto/Angstrom, checkout the hash which they've
just committed the v3.8.10 kernel for building and copied the patches
and configuration file
* I applied those patches to ipipe. It failed in one patch, but when I
saw, it was just #include positions. I corrected by hand.
* Executed scripts/prepare-kernel.sh, to install Xenomai patches
* Run menuconfig, to correct the real time part of the configuration file
* Build the kernel. It worked straight
* Copied the uImage file to the board

* Compiled Xenomai and installed to the board. In my case, I created a
recipe and installed the ipk file into my image.

I'll try to organize it in order to have an easier way to have it done.

Best regards,

Flavio


2013/6/8 Flavio Castro Alves Filho <flavio.alves@gmail.com>:
> Hello,
>
> 2013/6/5 Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>:
>> On 06/05/2013 05:42 PM, Michael Haberler wrote:
>>
>>> just letting you know I'm working with Robert Nelson to tack on a
>>> Xenomai kernel build to his automated build the thread is here:
>>> http://eewiki.net/display/linuxonarm/BeagleBone+Black+Comments (cant
>>> link to the actual post, search for xenomai)
>
> I'm currently working on a similar activity - have Linux Xenomai
> working on BeagleBone Black.
>
>>>
>>> this flow already produces the vanilla kernels which are in the BB
>>> Ubuntu and Debian images; the process is outlined here:
>>> http://tinyurl.com/n5ly89t ; the xenomai kernel(s) would be tacked
>>> onto this stream: http://rcn-ee.net/deb/wheezy-armhf/
>>>
>>> for now I'll use the patches Stephan had forwarded me in private, and
>>> switch on next release (suggestions to do better than that welcome)
>>
>>
>> You should probably use the ipipe-next branch in ipipe git tree.
>
> I'm sorry for my probably newbie question, but how should I use the
> ipipe git tree?
>
>>
>> --
>>                                                                 Gilles.
>>
>> _______________________________________________
>> Xenomai mailing list
>> Xenomai@xenomai.org
>> http://www.xenomai.org/mailman/listinfo/xenomai
>
>
>
> --
> Flavio de Castro Alves Filho
>
> flavio.alves@gmail.com
> www.linuxembarcado.com
> Twitter: http://twitter.com/#!/fraviofii
> LinkedIn profile: www.linkedin.com/in/flaviocastroalves



-- 
Flavio de Castro Alves Filho

flavio.alves@gmail.com
www.linuxembarcado.com
Twitter: http://twitter.com/#!/fraviofii
LinkedIn profile: www.linkedin.com/in/flaviocastroalves


  reply	other threads:[~2013-06-08 22:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 15:42 [Xenomai] Beaglebone kernels - automated builds WIP Michael Haberler
2013-06-05 18:32 ` Gilles Chanteperdrix
2013-06-07  5:52   ` Michael Haberler
2013-06-08 20:17   ` Flavio Castro Alves Filho
2013-06-08 22:46     ` Flavio Castro Alves Filho [this message]
2013-06-09  2:00     ` Michael Haberler

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=CAFNBftcwKG_t_wEOwHaE850UCo7aHprtpf2HU83_H0MKH71p-Q@mail.gmail.com \
    --to=flavio.alves@gmail.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.