From: Ambrogio <ambrogio.dadda@misarc.com>
To: ecos-discuss@ecos.sourceware.org
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] ethernet link status
Date: Wed, 25 Aug 2004 13:51:00 -0000 [thread overview]
Message-ID: <1093441910.991.41.camel@cad-00> (raw)
Dear all
On application using eCos it's possible to know the ethernet phisical
link status (eth0 or eth1)? It's possible to know if the link is active
(or down) whitout send packet over the link?
I so, I think it is a stupid question but afther two working day have no
solution for this problem.
Thanks in advance
Best regard for every answer (also a ... kill me).
By
Ambrogio
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
WARNING: multiple messages have this Message-ID
From: Ambrogio <ambrogio.dadda@misarc.com>
To: ecos-discuss@ecos.sourceware.org
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] ethernet link status
Date: Wed, 25 Aug 2004 15:13:00 -0000 [thread overview]
Message-ID: <1093441910.991.41.camel@cad-00> (raw)
Message-ID: <20040825151300.c2ucSKNbTbjiJ7dN6Gj9aSG8I7BwChR_1RdKTs-GGmg@z> (raw)
Dear all
On application using eCos it's possible to know the ethernet phisical
link status (eth0 or eth1)? It's possible to know if the link is active
(or down) whitout send packet over the link?
I so, I think it is a stupid question but afther two working day have no
solution for this problem.
Thanks in advance
Best regard for every answer (also a ... kill me).
By
Ambrogio
--
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 reply other threads:[~2004-08-25 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 13:51 Ambrogio [this message]
2004-08-25 15:13 ` Ambrogio
2007-09-27 7:46 [ECOS] Ethernet Link status Emmanuel Coullien
2007-09-27 11:17 ` Gary Thomas
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=1093441910.991.41.camel@cad-00 \
--to=ambrogio.dadda@misarc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--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).