[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [rtl] New release: uniprocessor 2.0.35
On Sat, 1 Aug 1998 yodaiken@chelm.cs.nmt.edu wrote:
>
> There is a ridiculously untested version of RTLinux for the 2.0.35
> Linux patch. I've reorganized for, what I hope, is simpler installation
> and to make the upcoming non-x86 versions fit in better. Please test
> and send comments.
>
> ftp://ftp.rtlinux.org/pub/rtlinux/release9
>
This release seems to constantly dump a hex value to the console (e.g.:
"00000018 :" is constantly dumped by the measurement module while the
frank example shows a variety of values, "0000001c :", "0000001d :",
etc., on each execution of the linux side exec). I didn't see any printk
statements like this in the source, where are these messages originating?
Also, the measurement demo seems to give a number of values for its min
max output, these values are quite unlike the 2.0.33 0.6 version:
min: -3, max: 25
min: -4, max: 2002
min: -3, max: 24
min: -3, max: 23
min: -4, max: 28
min: -3, max: 25
min: -3, max: 25
min: -4, max: 2003
min: -3, max: 23
min: -4, max: 23
min: -3, max: 23
min: -3, max: 25
min: -4, max: 2016
min: -3, max: 27
min: -3, max: 33
min: -4, max: 25
min: -3, max: 25
min: -3, max: 27
min: -3, max: 1983
min: -3, max: 28
min: -4, max: 28
min: -3, max: 25
The 0.6 version always gave 4 and 36 (or maybe 76), it looks like
something has changed here which is resulting in longer switching times;
is that a correct interpretation?
I am running 2.0.35 and "release9" on a P166 with display via X/vnc over
a tulip fast ether card.
Thanks for rt-linux!
-Don
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail majordomo@rtlinux.cs.nmt.edu OR
echo "unsubscribe rtl <Your_email>" | mail majordomo@rtlinux.cs.nmt.edu