All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <tbultel@free.fr>
To: xenomai@xenomai.org
Subject: [Xenomai] Some questions and issues about Xenomai 3
Date: Sun, 16 Nov 2014 11:01:37 +0100	[thread overview]
Message-ID: <54687601.5020805@free.fr> (raw)

Hi,
I am currently attempting to port my application from xenomai-2.6.(3/4) 
to xenomai-3-rc2

My application uses the canfestival package, which uses rt_socket_can.
The distribution is buildroot, and I have hacked it a little to support 
the build of mercury, because it is not supported yet.

For info, I have basically added this:
XENOMAI_CONF_OPT += --with-core=mercury
XENOMAI_CONF_OPT += --enable-smp
XENOMAI_CONF_OPT += --enable-pshared
XENOMAI_CONF_OPT += --enable-registry

I am encountering several issues:

1) xeno-config
a) it says an error with posix skin
localuser@thierry-desktop ~/workspace/agv (STD_ITG_15.03)*$ 
/nous/BASYSTEMES/buildroot/buildroot_agv_v15_amos820/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/bin/xeno-config 
--skin=posix --cflags
unknown RTOS skin: posix

b) --compat fails, and is not mentioned in the Usage
 
/nous/BASYSTEMES/buildroot/buildroot_agv_v15_amos820/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/bin/xeno-config 
--skin=native --cflags --compat
-I/usr/include/xenomai/mercury -I/usr/include/xenomai 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe 
-Os -D_GNU_SOURCE -D_REENTRANT -D__MERCURY__ -I/usr/include/xenomai/alchemy
Usage xeno-config OPTIONS
Options :
         --help
         --v,--verbose
         --version
         --cc
         --ccld
         --arch
         --prefix
         --[skin=]posix|vxworks|psos|alchemy|rtdm|smokey
         --auto-init|no-auto-init
         --cflags
         --ldflags
         --lib*-dir,--libdir,--user-libdir
         --core
         --info

c) provided that is should work, and that b) is related to an error of 
mine, would --compat fix the headers issue for applications that 
explicitly use #include <native/...> ? For now and testing I have SEDed 
them.

2) I have read in the manual that rtcan.h has been renamed to can.h
But after the install step, can.h is not installed in the staging.
buildroot was using "make install-user" for doing so. Changing to "make 
install" does not help.

3) More general question, about rtcan:
prepare_kernel.sh seems definitively needed for Cobalt kernel only. So 
how can the rtcan drivers be built in the PREEMPT_RT kernel ?
Sorry for my dummy question.

Regards
Thierry


             reply	other threads:[~2014-11-16 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 10:01 Thierry Bultel [this message]
2014-11-16 11:02 ` [Xenomai] Some questions and issues about Xenomai 3 Philippe Gerum

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=54687601.5020805@free.fr \
    --to=tbultel@free.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.