From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Interfacing directly to the low level ethernet driver, how??
Date: Thu, 28 Jun 2007 15:34:00 -0000 [thread overview]
Message-ID: <f60htp$iff$1@sea.gmane.org> (raw)
In-Reply-To: <4683BC51.5030502@mlbassoc.com>
On 2007-06-28, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> I'm about to develop a raw ethernet driver. After spending
>>>> quite a lot of time reading the forum and analyzing the code I
>>>> finally decide to implement a raw I/O API as suggested by
>>>> Grant Edwards here:
>>>
>>>> http://www.cygwin.com/ml/ecos-discuss/2003-06/msg00017.html
>>>
>>> What's the point of this? Couldn't you solve your problem by
>>> using RAW sockets?
Yes, if RAW sockets were supported by eCos.
>>> The reason for asking is just to point out that your ethernet
>>> "wire" will be pretty useless except for whatever raw traffic
>>> you push across it.
No, the raw I/O API peacefully coexists with the normal network
stack API. All network traffic that doesn't use the configured
proprietary Ethernet protocol number works the same as always.
>> Could you plase be more precise? I don't thing I got your
>> question, I thought that the version of FreeBSD on eCos didn't
>> implement RAW sockets. Or at least that's what I understood
>> from previous threads here. Am I wrong?
>
> Indeed, RAW sockets are not [currently] implemented. My
> question was what do you need that RAW sockets cannot provide?
> I think it would be a *much* simpler task to get RAW sockets
> working within the existing stack than to write your own
> networking layer.
It's a pretty thin layer -- it just allows you to queue up
outbout packets with cyg_io_write() and read from a queue of
inboung packets (with a specified protocol type) using
cyg_io_read().
Using RAW sockets would be nice, but adding a little code to an
in-house driver is logistically easier than adding raw socket
support to an "off-the-shelf" network stack and then turning
around and doing it all again a couple years later when the
network stack changes.
--
Grant Edwards grante Yow! Now that I have my
at "APPLE", I comprehend COST
visi.com ACCOUNTING!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-06-28 15:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 21:10 [ECOS] " Michele Paselli
2007-06-28 13:27 ` Andrew Lunn
2007-06-28 13:35 ` Gary Thomas
2007-06-28 13:49 ` Michele Paselli
2007-06-28 15:31 ` Gary Thomas
2007-06-28 15:34 ` Grant Edwards [this message]
2007-06-28 15:48 ` [ECOS] " Gary Thomas
2007-06-28 22:57 ` Grant Edwards
2007-07-02 12:10 ` [ECOS] " Michele Paselli
2007-07-02 12:19 ` Gary Thomas
2007-07-02 12:37 ` Michele Paselli
2007-07-02 12:48 ` Gary Thomas
2007-07-05 15:41 ` Michele Paselli
2007-07-02 14:50 ` [ECOS] " Grant Edwards
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='f60htp$iff$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).