From: Grant Edwards <grante@visi.com>
To: Bart Veer <bartv@cygnus.co.uk>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Re: Ethernet and Serial drivers for Linux target?
Date: Thu, 11 Nov 1999 09:45:00 -0000 [thread overview]
Message-ID: <19991111114526.B29982@visi.com> (raw)
In-Reply-To: <199911111737.RAA02373@sheesh.cygnus.co.uk>
On Thu, Nov 11, 1999 at 05:37:29PM +0000, Bart Veer wrote:
> It may be better to look at syscall-i386-linux-1.0.S in the synthetic
> target HAL sources.
I've browsed through there already, and that looks like a good
starting point.
> Note that if you want more realistic device driver behaviour, with
> interrupts etc.,
Naturally one would.
> then you will want to experiment with asynchronous I/O, SIGIO
> signals, etc.
Never done async I/O before, never done direct system calls before,
been using eCOS for two weeks. I'm practically an expert.
> If an eCos thread performs a blocking Linux read() syscall then you
> will block the entire eCos application, which is probably not what
> you want.
Of course not.
> Of course this makes the problem a bit more challenging :-)
If was easy everybody could do it, and then how could I walk around
feeling so superior?
--
Grant
prev parent reply other threads:[~1999-11-11 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-10 12:38 [ECOS] " Grant Edwards
1999-11-10 16:40 ` Gary Thomas
1999-11-11 4:44 ` [ECOS] " Bart Veer
1999-11-11 9:10 ` [ECOS] " Jonathan Larmour
1999-11-11 9:23 ` Grant Edwards
1999-11-11 9:32 ` Gary Thomas
1999-11-11 9:39 ` Grant Edwards
1999-11-11 9:37 ` [ECOS] " Bart Veer
1999-11-11 9:45 ` Grant Edwards [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=19991111114526.B29982@visi.com \
--to=grante@visi.com \
--cc=bartv@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).