public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: 宋宜叡 <ijsung@csie.nctu.edu.tw>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Microwindows on eCos
Date: Fri, 13 Apr 2001 06:55:00 -0000	[thread overview]
Message-ID: <XFMail.20010413075513.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <006601c0c39a$0c4237a0$0e79718c@biou>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

On 12-Apr-2001 §º©yèû wrote:
> Hi,
>  In the microwidows-eCos over iPaq port, I have several questions:
>     1. In ecos/nanox_thread.c (I assume it is the main nano-x server
> thread),
>         the code appears that nothing but the nanox_main() is called, but I
> can't find its implementation anywhere.

It's created by magic using #define in the Makefiles.

>     2. The original client/server IPC mechanism used in microwindows is Unix
> domain socket+Sys V shared memory
>         but what's the IPC mechanism used in the eCos port? TCP/IP socket?

Normal socket I/O over the loopback network.

>     3. What is the job of sytem threads in the port?
>  Or is there any documentations about that port?

The rest are used by the TCP/IP stack.

  reply	other threads:[~2001-04-13  6:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 14:36 宋宜叡
2001-04-13  6:55 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-27 17:05 Antoine.Amirault
2003-07-17 15:59 [ECOS] MicroWindows " Chris Garry
2003-07-17 16:17 ` Bob Koninckx
2003-07-17 16:43   ` Chris Garry
2003-07-18  4:40 ` Jonathan Larmour
2003-07-18 15:51   ` Chris Garry
2003-04-06  8:05 [ECOS] Microwindows " fairy
2003-04-07 22:17 ` Jonathan Larmour
2001-03-02  6:05 Rosimildo daSilva
2001-03-01 14:34 Rosimildo daSilva
2001-03-02  1:53 ` wangwei
2001-03-02  2:42   ` Rafael Rodríguez Velilla
2001-03-02  2:57     ` Martin van Veen
2001-03-02  3:48     ` Christian Plessl
2001-01-16  2:46 Á¶¼¼Çü
2001-02-28 17:47 ` wangwei
2001-03-01  4:01   ` Robin Farine

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=XFMail.20010413075513.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=ijsung@csie.nctu.edu.tw \
    /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).