All of lore.kernel.org
 help / color / mirror / Atom feed
From: raespi <raespi@icid.cu>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] about switchtest ...
Date: Mon, 04 Feb 2013 16:28:06 -0500	[thread overview]
Message-ID: <511027E6.4080202@icid.cu> (raw)
In-Reply-To: <51102316.9090107@xenomai.org>

Well we have a very big team working with linux on the smdk2440, from 
what we've seen, the 3.4 version breaks the audio in a very weird way.   
We're also merging other changes like the ones from the AF_DBUS project, 
but they're using other versions and it's a bit complicated.  Still all 
our changes will be submitted back to you ... I want to test Xenomai a 
bit more and see how it improves my system's response times, when I have 
more info I will send the full changes ...

Thanks again ..

El 02/04/2013 04:07 PM, Gilles Chanteperdrix escribió:
> On 02/04/2013 10:02 PM, raespi wrote:
>
>>   Right, I'm using these tools and options:
>>
>> *- toolchain:*
>> 4.6.3 (Sourcery CodeBench Lite 2012.03-57)
>>
>> *- configure options ( Running under buildroot, no special recipe, it
>> comes with one for the 2.6.0 version ):*
>> $ ./configure --target=arm-linux --host=arm-linux
>> --build=i686-pc-linux-gnu --prefix=/usr --exec-prefix=/usr
>> --sysconfdir=/etc --program-prefix= --disable-gtk-doc --enable-ipv6
>> --enable-static --enable-shared --includedir=/usr/include/xenomai/
>>
>> *- Prepin' the kernel:*
>> $(XENOMAI_DIR)/scripts/prepare-kernel.sh --linux=$(LINUX_DIR) --arch=arm
>> --adeos=adeos-ipipe-3.1.10-arm-001.patch
>>
>> I think I saw the problem.   Buildroot doesn't pass the " -march=armv4t
>> -msoft-float"  CFLAGS and LDFLAGS options to the xenomai configure line
>> for the s3c24xx.  At least the *xeno-test* is running now ...
>
> Good news. It is strange that not passing these options does not cause
> other run-time errors though (like invalid instructions).
>
>> Thanks for your time, are you interested in the complete patch for the
>> 3.1.10 version ?? ...
>
> Yes, that is interesting, but 3.1 is a bit old, I am not sure you have
> all the fixes, any reason for not using 3.2?
>
> Please keep the mailing list in CC.
>




  reply	other threads:[~2013-02-04 21:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 18:28 [Xenomai] about switchtest raespi
2013-02-04 18:31 ` Gilles Chanteperdrix
2013-02-04 19:22   ` raespi
2013-02-04 19:55     ` Gilles Chanteperdrix
2013-02-04 20:30       ` Jan Kiszka
2013-02-04 21:14         ` Gilles Chanteperdrix
     [not found]       ` <511021FC.7080906@icid.cu>
2013-02-04 21:07         ` Gilles Chanteperdrix
2013-02-04 21:28           ` raespi [this message]
2013-02-05 13:34             ` raespi
2013-02-05 14:26               ` Gilles Chanteperdrix
2013-02-05 14:52               ` Gilles Chanteperdrix
2013-02-05 14:56                 ` raespi
2013-02-05 14:59                   ` Gilles Chanteperdrix
2013-02-05 15:18                     ` raespi
2013-02-05 15:25                       ` Gilles Chanteperdrix
2013-02-05 15:31                         ` raespi
2013-02-05 15:32                           ` Gilles Chanteperdrix
2013-02-05 15:38                             ` raespi
2013-02-05 15:58                               ` 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=511027E6.4080202@icid.cu \
    --to=raespi@icid.cu \
    --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.