From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Nicolas SCHURANDO <schurann@ext.essilor.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] (no subject)
Date: Fri, 21 Aug 2015 11:26:04 +0200 [thread overview]
Message-ID: <20150821092604.GA12742@hermes.click-hack.org> (raw)
In-Reply-To: <CA+CJOCyg6wC9=kOi_XTB2pvrv3EdafLLGqd2TcHgt=KOYWWCNQ@mail.gmail.com>
On Fri, Aug 21, 2015 at 11:18:47AM +0200, Nicolas SCHURANDO wrote:
> Hi Mohamed,
>
> What version of xenomai are you using ? I am going to assume 2.6.x. I
> haven't worked with 3.x yet, and its architecture being different, I don't
> think the following instructions would apply for it.
>
> Installation of xenomai as explained at
> http://www.xenomai.org/documentation/xenomai-head/pdf/README.INSTALL.pdf is
> achieved through these steps :
>
> 1. If you are using a non-vanilla kernel, you should check for a
> possible pre-patch specific for your kernel.
>
> 2. Prepare your kernel by using the prepare-kernel.sh script.
>
> 3. Again, if you are using a non-vanilla kernel, check for a possible
> post-patch to apply.
>
> 4. Configure your kernel as you would normally do, through "make
> menuconfig" for example, and ensure the chosen configuration complies with
> xenomai requirements; see chapter "Kernel configuration" of
> http://www.xenomai.org/documentation/xenomai-head/pdf/TROUBLESHOOTING.pdf
>
> 5. Build your kernel, its modules, and deploy them on your target. At
> this point, you should see a few lines during early boot process if you
> type "dmesg | grep -i xenomai".
>
> 6. Finally, build the user-space binaries of xenomai, and deploy them on
> your target.
>
> Maybe someone can correct me if I am wrong, but I believe the
> "/proc/xenomai/version" pseudo-file is provided by the kernel, not by the
> user-space binaries. So, if it is missing on your board, it means something
> went wrong somewhere between steps 1 and 5.
The file is provided by the procfs pseudo-filesystem. If the /proc
directory is empty, chances are the /proc filesystem is not even mounted.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2015-08-21 9:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 11:58 [Xenomai] (no subject) Mohamed Fawzy
2015-08-19 16:32 ` [Xenomai] enabling Xenomai 2.x on udoo Philippe Gerum
2015-08-21 9:18 ` [Xenomai] (no subject) Nicolas SCHURANDO
2015-08-21 9:26 ` Gilles Chanteperdrix [this message]
2015-08-21 11:21 ` [Xenomai] بخصوص: " Mohamed Fawzy
2015-08-23 8:05 ` Mohamed Fawzy
2015-08-23 13:30 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2017-12-17 16:49 [Xenomai] " rajae rajae
2017-12-17 17:23 ` Greg Gallagher
2017-08-29 9:09 Xu Chen
2015-11-25 16:45 Umair Ali
2015-03-30 14:51 Helder Daniel
2014-05-01 23:58 alex.martin92
2013-07-22 7:27 Franz Engel
2013-03-27 16:23 Mohammadreza Babaee
2013-03-27 20:51 ` Gilles Chanteperdrix
2013-03-23 16:06 mfornero
2013-03-23 16:15 ` Gilles Chanteperdrix
2013-03-24 22:52 ` Gilles Chanteperdrix
2013-01-26 9:44 Amit Bhaira
2013-01-27 15:31 ` Gilles Chanteperdrix
2013-01-04 14:37 RAGHAVENDRA GANIGA
2012-12-15 8:49 Shamju Joseph
2012-12-15 11:50 ` 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=20150821092604.GA12742@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=schurann@ext.essilor.com \
--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.