All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maksym Veremeyenko <verem@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] mem usage and other application
Date: Sun, 18 Mar 2007 19:35:28 +0200	[thread overview]
Message-ID: <45FD7860.5030308@domain.hid> (raw)
In-Reply-To: <17917.29803.267170.622970@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

Gilles Chanteperdrix пишет:

>  >        1. Kernel 2.6.17.14, Xenomai 2.3.0... r2299, Adeos 1.5-02
> Here, I assume you mean Xenomai branch v2.3.x revision 2299
release 2.3.0 and branch v2.3.x revision 2299 - both

>  >        2. Kernel 2.6.19.2, Xenomai r2299, Adeos 1.7-01
> Here, I assume you mean Xenomai trunk revision 2299
yes

> The problem is that if there is no difference with regard to FPU context
> management between release 2.3.0 and latest revision of branch
> v2.3.x. So, the difference must be somewhere else.
What is recommended configuration and version of kernel and Xenomai?
In my case
2.6.20.3 upgrade failed due to Xenomai compilation,
2.6.19 fault gdb to work properly,
2.6.18 fail due to absent adeos-ipipe version.
I have to use 2.6.17.14 .....

> Could you send me your .config ?
attached


> Also, is it possible for you to try bisecting in v2.3.x branch ? v2.3.0
> release is revision 2004, and you know that revision 2299 does not work
> for you, so you would be able to tell us exactly which revision is the
> cause of your problem.
What trunk revisions should be tried?


-- 
________________________________________
Maksym Veremeyenko


[-- Attachment #2: config-2.6.17.14.xenomai-r2299.bz2 --]
[-- Type: application/x-bzip, Size: 6399 bytes --]

  reply	other threads:[~2007-03-18 17:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17913.899.384216.185459@domain.hid>
2007-03-15  9:11 ` [Xenomai-help] mem usage and other application Gilles Chanteperdrix
2007-03-15 16:34   ` Maksym Veremeyenko
2007-03-18 17:18     ` Gilles Chanteperdrix
2007-03-18 17:35       ` Maksym Veremeyenko [this message]
2007-03-18 18:23         ` Gilles Chanteperdrix
2007-03-19 15:17           ` Maksym Veremeyenko
2007-03-14 21:07 Maksym Veremeyenko
2007-03-14 21:26 ` Gilles Chanteperdrix
2007-03-14 22:38   ` Maksym Veremeyenko
2007-03-14 22:49     ` Gilles Chanteperdrix
2007-03-14 23:02       ` Maksym Veremeyenko
2007-03-14 23:05         ` Gilles Chanteperdrix
2007-03-14 23:27           ` Maksym Veremeyenko
2007-03-14 23:33             ` Gilles Chanteperdrix
2007-03-14 23:59               ` Maksym Veremeyenko
2007-03-15  0:18                 ` Gilles Chanteperdrix
2007-03-15  2:55                   ` Maksym Veremeyenko

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=45FD7860.5030308@domain.hid \
    --to=verem@domain.hid \
    --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.