Re: [liblo] ARM Cortex M3, uip, lwip, and liblo

Hey Steve,

Basically, none of the niceties of POSIX are there. No sockets, no poll, not
even gettimeofday().

I've just finished reading mostly all of the liblo source, and it looks to
me like send.c and server.c are going to need major surgery to rework them
so they do not use sockets. Everything 'above' this in liblo looks like
it'll be fine to use, with the exception of timetag.c, which relies on
time.h. Essentially, all that is available to me is a stripped down libc, so
at least malloc and calloc are there.

http://www.sics.se/~adam/uip/uip-1.0-refman/

There's the main uIP documentation. The closest thing they have to a socket
is a 'protosocket', which besides only being usable for TCP (which makes it
not very useful in my application) have some major limitations which make
them less useful than sockets. There's a nice description of them in the uIP
docs.

Since uIP doesn't provide sockets, the normal way liblo's 'server' concept
works is going to need to be inverted a little bit. Some event loop polling
the network for data will push new datagrams destined for liblo into the
liblo server, which will then parse them and deliver them.

I'd appreciate any input and advice you all have.

Thanks,
RJ

On Wed, Aug 11, 2010 at 4:43 PM, Stephen Sinclair <rad...@gm...>wrote:

> On Wed, Aug 11, 2010 at 4:26 PM, RJ Ryan <rr...@mi...> wrote:
> > Hi all,
> > I'm working on getting liblo working on a Cortex M3 ARM CPU. The network
> > stack I'm working with is uIP. Has anybody ever ported liblo to use
> either
> > lwIP or uIP?
>
> Not myself, but I'm interested in this.  Does this network stack
> differ significantly from the POSIX socket API?
>
> Steve
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>