[Olsr-dev] Antwort: Re: olsr0.5.5 ported to RTOS vxWorks from Windriver

(spam-protected) (spam-protected)
Thu Mar 20 10:26:26 CET 2008





Hello Hannes,

o.k., Give me some time to get Mercurial access and consolidate the code.

Thomas Martin
eMail: (spam-protected)


Hannes Gredler <(spam-protected)> schrieb am 18.03.2008 14:53:36:

> hi thomas,
>
> pls post your patch - i'd be happy to include this.
>
> /hannes
>
> On Tue, Mar 18, 2008 at 02:09:42PM +0100, (spam-protected)
> schwarz.com wrote:
> |
> |
> |
> |
> | Hi list,
> |
> | I am happy to announce the fact that OLSR is running fine on the real
time
> | operating system (RTOS) "vxWorks" (BSD based network stack) from
Windriver
> | Systems (www.windriver.com). The port is running on vxWorks6.4.
> |
> | I ported the OLSR version 0.5.5 to an embedded radio device (PowerPC)
and
> | tested functionality (incl. multihop, HNA) on 5 radios also with
multicast
> | messages.
> | For multicast I do not use the BMF plugin but a SMF (simplified
multicast
> | forwarding) version adapted and provided with OLSR informations.
> | Since we have no mass storage device in our system I could not use the
> | plugin infrastructure from OLSR. I linked some OLSR plugins statically.
> | The OLSR daemon is running in a single kernel task.
> | The ported plugins are:
> | - dot_draw
> | - dyn_gw
> | - httpinfo
> | And, of course, the base OLSR software with BSD stack interface. The
kernel
> | routing table is modified by OLSR.
> | The porting is mostly done by adding #ifdef's.
> |
> | During porting I found some bugs/corrections (e.g. adding/deleting
kernel
> | routes from BSD).
> | I do have permission to give this port to the community. So if anyone
has
> | interest I would do this ;-)
> |
> | I probably nedd to setup a Mercurial View? (Need to do that from
somewhere
> | else, because port numbers are blocked here)
> |
> | Thomas
> |
> |
> |
> | eMail: (spam-protected)
> |
> |
> | --
> | Olsr-dev mailing list
> | (spam-protected)
> | http://lists.olsr.org/mailman/listinfo/olsr-dev
> |





More information about the Olsr-dev mailing list