From: Robert Berger <gmane@reliableembeddedsystems.com>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] process behaviour when running xenomai
Date: Fri, 07 Mar 2014 23:14:19 +0200 [thread overview]
Message-ID: <531A36AB.9040009@reliableembeddedsystems.com> (raw)
In-Reply-To: <5319C7CA.1030701@xenomai.org>
Hi Gilles,
On 03/07/2014 03:21 PM, Gilles Chanteperdrix wrote:>
> Generally, before you report a non-working configuration of Xenomai,
> with a certain version of the kernel, please try the exact same kernel
> configuration without Xenomai.
>
>
I think I was not explicit enough in my previous email.
The problem that ethernet does not work is __NOT__ due to Xenomai!
It's a general problem with beagle-xm and 3.10 (and not just)
The workaround in theory is CONFIG_NOP_USB_XCEIV=M which will in best
case turn on the ethernet interface in user space and not allow the
kernel to load a rootfs over nfs.
My intention was to ask the op if he has the network up and running with
a 3.10 kernel and Xenomai.
Sorry for not being clear enough.
Regards,
Robert
...There's no time to stop for gas, we're already late.- Karin Donker
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2014-03-07 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:46 [Xenomai] process behaviour when running xenomai Huub Van Niekerk
2014-03-06 16:27 ` Gilles Chanteperdrix
2014-03-06 19:21 ` Gilles Chanteperdrix
2014-03-07 10:14 ` Robert Berger
2014-03-07 12:57 ` Gilles Chanteperdrix
2014-03-07 13:21 ` Gilles Chanteperdrix
2014-03-07 21:14 ` Robert Berger [this message]
2014-03-07 21:49 ` Gilles Chanteperdrix
2014-03-08 11:14 ` Huub Van Niekerk
2014-03-22 16:03 ` Robert Berger
2014-03-07 16:31 ` Gilles Chanteperdrix
2014-03-07 19:48 ` Huub Van Niekerk
2014-03-07 19:53 ` 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=531A36AB.9040009@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--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.