This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: R?f. : Re: Question on Posix Select function
- From: Andrew Lunn <andrew at lunn dot ch>
- To: e dot coullien at faiveley dot com
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 21 Jun 2006 09:33:15 +0200
- Subject: [ECOS] Re: R?f. : Re: [ECOS] Question on Posix Select function
- References: <C1257194.00286D4D.00@smtp.faiveley.fr>
On Wed, Jun 21, 2006 at 09:21:40AM +0200, e.coullien@faiveley.com wrote:
>
>
> 1) Our Instrument package stores Timebase, Events code, thread and 2 arguments
> and compress each frame and store the frame in a buffer, then when the buffer
> reach 1500 oct, it sends the buffer on Ethernet. This allow to reduce the number
> of instrument event.
So you are using the existing instrementation package to collect the
events and you have added code to output it to the network.
> We don't use the Redboot network stack because the PC software need to control
> the instrument package on the board in real time.
> For exemple, during the run, we can start or stop the trace, change events
> filter or we can ask the name and priority of each thread.
There is nothing there that the RedBoot network stack cannot do. It
allows real time debugging.
The advantage of using the RedBoot stack would be you don't have to
worry about it producing events in your log.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss