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 14:15:00 -0000 [thread overview]
Message-ID: <f14tkp$m1s$1@sea.gmane.org> (raw)
In-Reply-To: <20070430135828.GG28128@lunn.ch>
On 2007-04-30, Andrew Lunn <andrew@lunn.ch> wrote:
>> 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.
>
> Have you looked at porting the FreeBSD equivalent of SOCK_RAW.
> With any luck you just need to drop in a few files and it
> runs.
No, I don't think anybody's looked into that. It would be nice
to have standardized support, though it would mean giving up
the zero-copy feature of our current implementation. I've
always been a little surprised that there wasn't more demand
for the ability to support proprietary protocols in eCos
embedded devices.
--
Grant Edwards grante Yow! Are you still an
at ALCOHOLIC?
visi.com
--
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-04-30 14:15 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
2007-04-30 13:58 ` Andrew Lunn
2007-04-30 14:15 ` Grant Edwards [this message]
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='f14tkp$m1s$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).