I checked out xeno.trunk just a few minutes ago.
With kernel 2.4.32, kernel compilation fails with this:
mq.c: In function `mq_notify':
mq.c:475: error: `SIGEV_SIVNAL' undeclared (first use in this function)
mq.c:475: error: (Each undeclared identifier is reported only once
mq.c:475: error: for
Jan Kiszka wrote:
[...]
Yea, maybe that periodic timer mode is not compiled in and
rt_timer_start fails in your original example. I think it's off by
default now.
Yeah, got it! Sorry for not supplying error code earlier!
In Xeno source:
int xnpod_start_timer (u_long nstick, xnisr_t
Philippe Gerum wrote:
[...]
Just one question: what's the reason why the periodic mode
is disabled by default ?
Because AFAICT, most people would rather use the aperiodic timing mode
in usual configurations for a much better accuracy. Since the periodic
mode uses the available hw PIT and
Hi all!
Jan Kiszka wrote:
[...]
+printk(Xenomai: Intel chipset found but SMI workaround not enabled in
kernel\n
+configuration. You may encounter high interrupt
latencies.\n);
Speaking of printk. Since 2.1 I don't see any messages in the
kernel log. I bet there is a
Philippe Gerum wrote:
This time, the merge window is closed for good; no kidding. This said,
too many changes since -rc3 have taken place for releasing v2.1 without
one more -rc iteration, so here is -rc4. Major updates are as follows:
- scalable timer management using non-linear access
Hannes Mayer wrote:
Ciao Jan!
It doesn't seem to make a difference if one uses
RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
With RTDM_IRQ_NONE the IRQ should be passed to linux,
right ? But it doesn't seem to happen - this brought
up the top problem I've posted a few days ago.
Returning
Jan Kiszka wrote:
Hannes Mayer wrote:
Hannes Mayer wrote:
Ciao Jan!
It doesn't seem to make a difference if one uses
RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
With RTDM_IRQ_NONE the IRQ should be passed to linux,
right ? But it doesn't seem to happen - this brought
up the top problem I've posted
Romain Lenglet wrote:
During prepare-kernel.sh I noticed that
Adeos/i386 1. (newgen) installed.
Links installed.
Build system ready.
is not printed anymore. Bug or feature ?
Feature. --verbose brings this message back, IIRC. I guess
that's needed for automated Debian packaging stuff
Hi all!
Jan Kiszka wrote:
[...]
+printk(Xenomai: Intel chipset found but SMI workaround not enabled in
kernel\n
+configuration. You may encounter high interrupt
latencies.\n);
Speaking of printk. Since 2.1 I don't see any messages in the
kernel log. I bet there is a
Philippe Gerum wrote:
[...]
dmesg | grep -i xenomai: ?
Yeah, got it now!
Sorry for the silly question!
I forgot that as of 2.1 everything is compiled into the kernel
by default, so when running a testsuite example there are no
messages that xeno is loaded or unloaded.
Thanks and best
Hi all!
Well, subject says almost all.
I remember there has been an effort to make a fusion/rt-preempt
patch conglomerate back then.
I'm just curious (as I've just been toying with the Molnar
patch) - has that thing been dropped in xeno completely ?
Thanks and best regards,
Hannes.
Jan Kiszka wrote:
[...]
Do you (or anybody else) have a running 2.0.x installation? If so,
please test that setup as well.
Sure :-)
# uname -r
2.6.13.4-adeos-xenomai
# cat /proc/xenomai/version
2.0
# ./mutex
Running for 2.15 seconds.
ALERT: No lock! (lockcnt=0) Offending task: task0
ALERT: No
I checked out xeno.trunk just a few minutes ago.
With kernel 2.4.32, kernel compilation fails with this:
mq.c: In function `mq_notify':
mq.c:475: error: `SIGEV_SIVNAL' undeclared (first use in this function)
mq.c:475: error: (Each undeclared identifier is reported only once
mq.c:475: error: for
Hi Jan!
Jan Kiszka wrote:
Hannes Mayer wrote:
I checked out xeno.trunk just a few minutes ago.
With kernel 2.4.32, kernel compilation fails with this:
mq.c: In function `mq_notify':
mq.c:475: error: `SIGEV_SIVNAL' undeclared (first use in this function)
mq.c:475: error: (Each undeclared
Jan Kiszka wrote:
[...]
Yea, maybe that periodic timer mode is not compiled in and
rt_timer_start fails in your original example. I think it's off by
default now.
Yeah, got it! Sorry for not supplying error code earlier!
In Xeno source:
int xnpod_start_timer (u_long nstick, xnisr_t
Ciao Philippe!
prepare-kernel.sh works well - I'd suggest to ask the user for
the 3 needed parameters, instead of supplying them as parameters.
e.g.
# scripts/prepare-kernel.sh
Linux directory: [default: /usr/src/linux] :
Adeos-patch: [default: none] :
Architecture: [default: i386]
...or
Wolfgang Grandegger wrote:
[...]
I have realized the same error building out of the source tree for
PowerPC. The problem is, that the link is pointing to itself. Apart from
that, the ksrc part works fine (at least I can boot the ipipe kernel).
If I remove the sym-link and copy
Jan Kiszka wrote:
Bruno Rouchouse wrote:
On 10/25/05, Jan Kiszka [EMAIL PROTECTED] wrote:
The logo looks nice - who's the designer? Shouldn't (s)he work out the
image as well...?
I designed the logo. After a couple of beers I got inspired but I would need
to drink too much to obtain the
Hi all!
I'm back :-)
After some time on Mars (http://www.austromars.at) and some
vaccation, here are my test results:
kernel 2.4.32
Xeno2.2rc2
= testsuite works
= RTDM Driver Skeleton works
Best regards,
Hannes.
___
Xenomai-core mailing list
Ciao Philippe et al.!
Philippe Gerum wrote:
[...]
http://download.gna.org/xenomai/stable/xenomai-2.2.0.tar.bz2
Congratulations on the newest release! :-)
I've encountered a probably minor problem:
I compiled the 16550A driver as module (everything else into
the kernel), but when modprobing
...out of curiosity and to test an older example, I compiled
in periodic timer support, recompiled and then it oopses
at boot. Screenshot:
http://www.captain.at/tmp/dsc05081.jpg
*shrugs*
Best regards,
Hannes.
___
Xenomai-core mailing list
Hi Jan!
Jan Kiszka wrote:
[...]
When you THEN try compiling the driver within the kernel build again,
does it still work? I bet it will, because this was likely some issue of
a half-baked kernel. I also re-checked this and noticed no problems
loading the driver.
I didn't replace the original
Hi Jan!
Jan Kiszka wrote:
[...]
Hmm, 2.4 limitation. There used to by some tool called ksymoops for
this. Please give it a try.
hmm...so far I haven't figured out how to use ksymoops, but I got this:
# addr2line -e vmlinux -f c0126f46
__ipipe_dispatch_event
??:0
# addr2line -e vmlinux -f
Hi Jan!
Jan Kiszka wrote:
What about addr2line -e vmlinux -f c01d68b2?
# addr2line -e vmlinux -f c01d68b2
xnshadow_ppd_insert
shadow.c:0
Ok, will keep you posted!
Tante grazie e buon fine settimana,
Hannes.
___
Xenomai-core mailing list
Ciao Jan!
Jan Kiszka wrote:
[...]
Please try make clean before rebuilding your 2.4 kernel with a
Indeed, make clean does a wonder :-)
BTW, is there any way to reconfigure the periodic timer ?
Not that I wanna use it - I'm fine with the more accurate aperiodic
timer, but just curious.
This
Hi all!
Here are some suggestions for the xenomai.org website:
* no redirect from xenomai.org to
http://snail.fsffrance.org/www.xenomai.org/
* put real-time framework for linux into the page title
* add info why registering is cool and what benefits it
will offer
* make the top-most xeno
26 matches
Mail list logo
