From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: ecos <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] why is ether_aton not implemented?
Date: Thu, 18 Jul 2013 07:36:00 -0000 [thread overview]
Message-ID: <51E79AD4.3080304@televic.com> (raw)
Hi,
I need the function 'ether_aton'. The declaration is in <net/ethernet.h>
(or ecos/packages/net/bsd_tcpip/current/include/net/ethernet.h).
But there is no implementation in the eCos sources, why?
If the answer is "because nobody ever ported it from freeBSD", then
maybe better remove the declaration?
However, in ecos/packages/net/common/current/tests/bridge.c I do find an
implementation...
Regards,
Jürgen
--
Jürgen Lambrecht
R&D Associate
Mobile: +32 499 644 531
Tel: +32 (0)51 303045 Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk
--
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:[~2013-07-18 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51E79AD4.3080304@televic.com \
--to=j.lambrecht@televic.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).