public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: e.coullien@faiveley.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: R?f. : Re: [ECOS] Question on Posix Select function
Date: Wed, 21 Jun 2006 07:33:00 -0000	[thread overview]
Message-ID: <20060621073315.GM21228@lunn.ch> (raw)
In-Reply-To: <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

      reply	other threads:[~2006-06-21  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21  7:22 [ECOS] Réf. " e.coullien
2006-06-21  7:33 ` Andrew Lunn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060621073315.GM21228@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=e.coullien@faiveley.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).