public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Fwd: Sending raw packets on eCos
Date: Mon, 30 Apr 2007 13:52:00 -0000	[thread overview]
Message-ID: <f14sa3$ig0$1@sea.gmane.org> (raw)
In-Reply-To: <m33b2iyvbr.fsf@xl5.calivar.com>

On 2007-04-30, Nick Garnett <nickg@ecoscentric.com> wrote:

>>  So I believe the frames should be sent as raw ethernet
>>  frames...All the handling should be done in the application.
>>  As I ran through the archives there were some suggestions to
>>  use eth_drive_write() and eth_drive_read() found in
>>  eth_drv.c. I think these are internal functions used by eCos,
>>  which cannot be used in our application. Please if you can
>>  mention the names of the API's for raw ethernet I/O it would
>>  be very helpful..
>
> You have already named them above. Those are the only APIs
> available. However, they are closely linked in to the BSD
> stack and it will be hard to use them from application level.

I too would be interested in a way to send/receive raw Ethernet
packets.  The products I work on have to support a propritary
Ethernet protocol, and in the past we've always had to write
our own Ethernet drivers that implimented a normal
cyg_io_read/write() API in addition to the BSD network stack
API.

Obviously, some way to send/receive raw Ethernet packets (akin
to socket(AF_PACKET, SOCK_RAW, protoNumer) under Linux) would
save us a lot of work.

-- 
Grant Edwards                   grante             Yow! What's the MATTER
                                  at               Sid? ... Is your BEVERAGE
                               visi.com            unsatisfactory?


-- 
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:[~2007-04-30 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 10:18 [ECOS] " manesh
2007-04-26 13:35 ` Andrew Lunn
     [not found]   ` <1177738903.263455.239890@l77g2000hsb.googlegroups.com>
2007-04-28  9:53     ` [ECOS] Fwd: " manesh
2007-04-30  8:20       ` Nick Garnett
2007-04-30  9:53         ` [ECOS] " manesh
2007-04-30 10:16           ` Nick Garnett
     [not found]             ` <1177930381.251419.318920@y5g2000hsa.googlegroups.com>
2007-04-30 11:08               ` Nick Garnett
2007-04-30 13:52                 ` Grant Edwards [this message]
2007-04-30 13:58                   ` Andrew Lunn
2007-04-30 14:15                     ` Grant Edwards
2007-05-01 15:42                 ` manesh
2007-05-01 16:23                   ` Nick Garnett
2007-04-28 13:09   ` [ECOS] " manesh

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='f14sa3$ig0$1@sea.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.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).