From: edward.robbins@domain.hid
To: Thomas Lockhart <Thomas.Lockhart@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Supported cPCI systems
Date: Mon, 8 Nov 2010 16:14:05 -0000 (GMT) [thread overview]
Message-ID: <1289232845.384714670@domain.hid> (raw)
In-Reply-To: <4CD817BB.80404@domain.hid>
Hi, and thanks for your response. A couple of questions:
Does the PP421 work with consistently low latencies?
Did you need to modify Xenomai or the kernel at all?
Could you tell me what kernel and xenomai versions you are using?
Thanks,
Edward
On Monday, 8 November, 2010 3:31pm, "Thomas Lockhart" <Thomas.Lockhart@domain.hid> said:
>> since I have been unsuccessful getting Xenomai to work on our MEN
>> F19P and F17 systems, I would like to hear from anyone who has had
>> success with other cPCI based systems - preferably x86 with dual
>> processor support, but failing that anything will do at this point.
>
> We have had success with a dual-processor cPCI Xeon board from
> Concurrent Technologies (a PP421 I think).
>
> I have another board from them (a PP531 I think) which will not boot
> recent Linux kernels (past 2.6.27 or so) including the FC13 distro disk.
> The company claims FC13 is supported so I don't know what is up with
> that. So far they have not been helpful on that front. I haven't done
> much with Xenomai on that board but I think it builds and runs with a
> 2.6.26-based kernel.
>
> hth
>
> - Tom
>
next prev parent reply other threads:[~2010-11-08 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 10:23 [Xenomai-help] Supported cPCI systems edward.robbins
2010-11-08 15:31 ` Thomas Lockhart
2010-11-08 16:14 ` edward.robbins [this message]
2010-11-08 16:25 ` Thomas Lockhart
2010-11-08 20:12 ` Gilles Chanteperdrix
2010-11-08 20:22 ` Hemal C.Bavishi
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=1289232845.384714670@domain.hid \
--to=edward.robbins@domain.hid \
--cc=Thomas.Lockhart@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.