public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: "'eCos mailing list'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] i386 TARGET network programming
Date: Mon, 30 Jul 2001 13:01:00 -0000	[thread overview]
Message-ID: <005901c11932$65d8c9d0$090110ac@TRENT> (raw)
In-Reply-To: <3B65BC10.F2F26ECC@redhat.com>

  > 
  > "Trenton D. Adams" wrote:
  > >
  > >   >
  > >   > > Is there anyway of getting eCos to query the drivers in
linux
  > for
  > >   > > network capability?  If so, I imagine it would be a lot of
work
  > > right?
  > >   >
  > >   > Ummm... given they are completely different OS's, I don't
really
  > > know
  > >   > what
  > >   > you mean here. This isn't the synthetic target if that's what
  > you're
  > >   > thinking about.
  > >   >
  > >
  > > >From what I understand, don't eCos PC target programs run
directly as
  > > native Linux executables running an eCos OS which call on the
Linux
  > > kernel for various aspects of the eCos kernel?
  > 
  > That's the "synthetic Linux" target. The (real) PC target is a
proper
  > port
  > to PCs, which you can boot off a floppy, or with the right support,
even
  > program into flash.
  > 
  > >  I was sure I read that
  > > somewhere.   If so, can't a network driver be written that will do
a
  > > similar thing to gain access to all possible network card drivers
  > under
  > > linux?
  > 
  > Yes, but only the synthetic linux target :).
  > 

Oh, I see, thanks!  I'm going to ask a quick question about that in a
minute if I can't find it in the archives.

  reply	other threads:[~2001-07-30 13:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  7:47 Trenton D. Adams
2001-07-30 11:59 ` Jonathan Larmour
2001-07-30 12:14   ` Trenton D. Adams
2001-07-30 12:20     ` Jonathan Larmour
2001-07-30 12:34       ` Trenton D. Adams
2001-07-30 12:42         ` Jonathan Larmour
2001-07-30 12:46           ` Trenton D. Adams
2001-07-30 12:57             ` Jonathan Larmour
2001-07-30 13:01               ` Trenton D. Adams [this message]
2001-07-30 13:44               ` Trenton D. Adams
2001-07-30 13:46                 ` Jonathan Larmour
2001-07-30 16:39                   ` [ECOS] RM7000 interrupt handling Chris Morrow
2001-07-31  5:53                     ` Hugo Tyson
2001-07-31  6:13                       ` Mark Salter
2001-07-31  7:17                         ` Robin Farine
2001-07-31  9:43                           ` Hugo Tyson
2001-07-31  9:59                             ` Robin Farine
2001-07-31 10:28                             ` Chris Morrow
2001-07-31 11:08                               ` Hugo Tyson
2001-08-02  6:32                           ` Hugo Tyson
2001-08-02  7:47                             ` Robin Farine
2001-08-02  8:08                               ` Hugo Tyson
2001-07-30 16:47       ` [ECOS] i386 TARGET network programming Fabrice Gautier
2001-07-31 14:33         ` Jonathan Larmour
2001-07-31 14:36           ` Jonathan Larmour
2001-07-31 14:44             ` Jonathan Larmour
2001-07-31 16:12               ` Fabrice Gautier
2001-07-31 17:49                 ` Jonathan Larmour
2001-07-30 13:22     ` Fabrice Gautier

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='005901c11932$65d8c9d0$090110ac@TRENT' \
    --to=tadams@extremeeng.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.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).