<br><font size=2 face="sans-serif">Hi all,</font>
<br>
<br><font size=2 face="sans-serif">i have an error with sparc-rtems-4.7.99.2-gcc-4.2.1-1.0.0-linux.tar.bz2
that I got from Gaisler research. The RTEMS version within this package
is 4.8 . </font>
<br><font size=2 face="sans-serif">I got a piece of SW already compiled
and proved with RTEMS 4.6. When I updated to the 4.8 RTEMS version and
tried to re-compile the SW I got a linker error:</font>
<br>
<br><font size=2 face="sans-serif">/opt/rtems-4.8/sparc-rtems/leon2/lib/librtemsbsp.a(libnetchip_a-smc91111.o):
In function `lan91cxx_interrupt_handler':</font>
<br><font size=2 face="sans-serif">/home/daniel/reps/rtems48_rep/rtems-4.8-build/sparc-rtems/c/leon2/libchip/../../../../../rtems-4.8/c/src/libchip/network/smc91111.c:121:
undefined reference to `DEBUG_puts'</font>
<br>
<br><font size=2 face="sans-serif">The strange thing here is that the path
/home/daniel/reps...etc etc does not exist in my machine. I think maybe
this is an error of the compiled version I got.</font>
<br>
<br><font size=2 face="sans-serif">any clue?</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>rtems skyeye <skyeye.rtems@gmail.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: rtems-users-bounces+aitor.viana.sanchez=esa.int@rtems.org</font>
<p><font size=1 face="sans-serif">03/09/2007 16:50</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">rtems-users@rtems.org, yanmiaobest@gmail.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">SPAM:**** Fwd: design Real-Time Process
in RTEMS</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br><font size=3 face="sans-serif">hi, </font>
<br><font size=3 face="sans-serif"> Good idea!</font>
<br><font size=3 face="sans-serif"> I think we can first realize
the initial VM support in RTEMS.</font>
<br><font size=3 face="sans-serif"> because there are
already some page support funcs in rtems X86 port.</font>
<br><font size=3 face="sans-serif"> then we can try syscall,....</font>
<br><font size=3 face="sans-serif"> </font>
<br><font size=3 face="sans-serif"> </font>
<br>
<br><font size=3 face="sans-serif">---------- Forwarded message ----------
</font>
<br><font size=3 face="sans-serif">From: <b>رضيµ</b> <</font><a href=mailto:yanmiaobest@gmail.com><font size=3 color=blue face="sans-serif"><u>yanmiaobest@gmail.com</u></font></a><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">Date: Sep 3, 2007 11:21 AM</font>
<br><font size=3 face="sans-serif">Subject: Re: design Real-Time Process
in RTEMS </font>
<br><font size=3 face="sans-serif">To: rtems skyeye <</font><a href=mailto:skyeye.rtems@gmail.com><font size=3 color=blue face="sans-serif"><u>skyeye.rtems@gmail.com</u></font></a><font size=3 face="sans-serif">></font>
<br>
<br><font size=3 face="sans-serif">Hi:</font>
<br>
<br><font size=3 face="sans-serif"> I have been thinking about
it too.</font>
<br><font size=3 face="sans-serif"> here is what I think:</font>
<br>
<br><font size=3 face="sans-serif"> 1. page routine
should be created to support page manipulations( </font>
<br><font size=3 face="sans-serif">page table operation, TBL, page allocate,
set page state ...)</font>
<br><font size=3 face="sans-serif"> 2. identify
all system call routines</font>
<br><font size=3 face="sans-serif"> 3. create entry
points and exit points for system call</font>
<br><font size=3 face="sans-serif"> 4. adjust context
switch ralated routine</font>
<br><font size=3 face="sans-serif"> 5. add privilege
transition code</font>
<br>
<br><font size=3 face="sans-serif"> best regards!</font>
<br>
<br><font size=3 face="sans-serif">2007/8/31, rtems skyeye <</font><a href=mailto:skyeye.rtems@gmail.com><font size=3 color=blue face="sans-serif"><u>skyeye.rtems@gmail.com</u></font></a><font size=3 face="sans-serif">>:</font>
<br><font size=3 face="sans-serif">> hi,</font>
<br><font size=3 face="sans-serif">> VxWorks 6.x have the
Real-Time Process (RTP) extension. </font>
<br><font size=3 face="sans-serif">> I think we also can
implement the RTP in RTEMS.</font>
<br><font size=3 face="sans-serif">> The Idea is :</font>
<br><font size=3 face="sans-serif">> 1 RTP contains 1~n
user-level rtems-task, and process the</font>
<br><font size=3 face="sans-serif">> virtual memory related things.</font>
<br><font size=3 face="sans-serif">> 2 the mapping relation
of virtual memory :phyiscal memory is 1:1 </font>
<br><font size=3 face="sans-serif">> 3 the user-level task
in RTP can access kernel function</font>
<br><font size=3 face="sans-serif">> by syscall</font>
<br><font size=3 face="sans-serif">> 4 the user-level tasks
and the kernel-level tasks are in the same</font>
<br><font size=3 face="sans-serif">> scheduling strategy.</font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">> the advantage of RTP
is: </font>
<br><font size=3 face="sans-serif">> 1 the crash
of user-level tasks in RTP can not destroy user-level</font>
<br><font size=3 face="sans-serif">> tasks in other RTP and the kernel.</font>
<br><font size=3 face="sans-serif">> 2 compatible
with the old task model.</font>
<br><font size=3 face="sans-serif">> 3 the context
switch is faster than that of general OS (such as linux) </font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">> anyone have some
advices on RTP in RTEMS?</font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">> Regards</font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">> skyeye.rtems</font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">> _______________________________________________</font>
<br><font size=3 face="sans-serif">> rtems-users mailing list </font>
<br><font size=3 face="sans-serif">> </font><a href="mailto:rtems-users@rtems.com"><font size=3 color=blue face="sans-serif"><u>rtems-users@rtems.com</u></font></a>
<br><font size=3 face="sans-serif">> </font><a href="http://rtems.rtems.org/mailman/listinfo/rtems-users"><font size=3 color=blue face="sans-serif"><u>http://rtems.rtems.org/mailman/listinfo/rtems-users</u></font></a>
<br><font size=3 face="sans-serif">></font>
<br><font size=3 face="sans-serif">></font>
<br>
<br><font size=2><tt>_______________________________________________<br>
rtems-users mailing list<br>
rtems-users@rtems.com<br>
http://rtems.rtems.org/mailman/listinfo/rtems-users</tt></font>
<br>
<br>