public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Emmanuel Coullien <coullien.emmanuel@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Ethernet Link status
Date: Thu, 27 Sep 2007 11:17:00 -0000	[thread overview]
Message-ID: <46FB9125.9080909@mlbassoc.com> (raw)
In-Reply-To: <3fae21000709270046v974f8d5ne0514658da35e542@mail.gmail.com>

Emmanuel Coullien wrote:
> Hi,
> 
> I tryed to know what was the Ethernet link status from the application
> level using ioctl but I think it miss some code in the BSD_TCPIP
> package to pass over this layer.
> In fact, it misses the case for SIOCGSTATUS in the BSD_TCPIP layer, so
>  I had to add the lines below in the if.c file and now we can get the
> link status.
>  	case SIOCGIFSTATUS:
> 	case SIOCGIFSTATS:
> 	case SIOCGIFSTATSUD:
> 		if (ifp->if_ioctl == 0)
> 			{
> 			return (EOPNOTSUPP);
> 			}
> 		return ((*ifp->if_ioctl)(ifp, cmd, data));
> 
> What do you think about these modifications. Is it possible to patch
> it in eCos ?
> 

Thanks. I've applied a similar, but equivalent, change.

In the future, if you find a change that you think needs to
be made, send a proper patch, along with a ChangeLog entry,
to ecos-patches@ecos.sourceware.org.  We'll discuss and
consider the change, and apply as required.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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-09-27 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  7:46 Emmanuel Coullien
2007-09-27 11:17 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-25 13:51 [ECOS] ethernet link status Ambrogio
2004-08-25 15:13 ` Ambrogio

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=46FB9125.9080909@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=coullien.emmanuel@gmail.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).