Hello Jakub,
I have examined your ping patch and pushed a changeset based on it to
our mainline branch (revision 1907). Except for some minor coding style
changes along the way please note the following modifications:
* I have split your original ping_repeat_count variable into two
variables: One unsigned integer for the (finite) repeat count and one
boolean flag for the infinite repeating.
* I have altered the use of the two conditional variables, they now act
hierarchically (received_cv signals only to the transmit_fibril and
done_cv signals only to the main fibril). Also, the signal value for
the transmit_fibril is now tri-state to always distinguish a timeout,
a successful reply and the user interruption.
* The return value of getopt() is int. Char cannot be used because
it is unsigned on some platforms such as arm32 (but the condition in
the while loop compares the value to -1).
I have also adapted your modifications for ping6. Anyway thanks for the
contribution!
Was that configuration tested on this board? Will it be time-consuming to
set working environment on that board?
Yes, it was tested, but it was also some 4 years ago. The configuration
of the LEON design required some manual modifications (it was not even
the vanilla set of VHDL files from Gaisler Research, some custom patches
from the board vendor were required) and the tools were rather
unfriendly (also Windows-only, if I remember correctly).
It is possible to make it work, but it is not straightforward and it
takes some time. I suggest trying the other viable options first.
Maybe there are some pre-synthesized configurations working on certain
FPGA chips out-of-the-box?
Yes, there are. But such FPGA boards are definitively not in the "not
expensive" category.
M.D.
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
