All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: p.vonbrunn@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Unable to use Xenomai-Services on ARM/S3C2410
Date: Mon, 30 Mar 2009 12:01:07 +0200	[thread overview]
Message-ID: <49D09863.9080008@domain.hid> (raw)
In-Reply-To: <20090330061745.D3E7A90005@domain.hid>

p.vonbrunn@domain.hid wrote:
> The problem with updating the kernel is the platform-specific patch
> (additional devices etc.), which is very huge and only available for
> 2.6.19. The latency-test doesn't seem to run: Illegal Instruction is the
> output I get. Did I miss anything?

I do not intend to spend time on bugs which have already been fixed.

And nobody asks you to port your whole board-specific support to 2.6.28
to just run latency. You only need support for serial port, and maybe
ethernet driver if you intend to run the test over NFS.

Now, the only two bugs which come to my mind are:
- EABI setting
- gcc version (you can only use gcc up to 4.1 with this revision of
xenomai).

Also note that nowadays, maintaining forks of the Linux kernel for
specific boards is considered a bad way of getting linux to support your
board, one reason being precisely the one you invoke: upgrading becomes
difficult.
See http://lwn.net/Articles/230831/

-- 
                                                 Gilles.


  reply	other threads:[~2009-03-30 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  6:17 [Xenomai-help] Unable to use Xenomai-Services on ARM/S3C2410 p.vonbrunn
2009-03-30 10:01 ` Gilles Chanteperdrix [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-27 11:59 p.vonbrunn
2009-03-27 13:35 ` Gilles Chanteperdrix
2009-03-27 13:56 ` 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=49D09863.9080008@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=p.vonbrunn@domain.hid \
    --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.