public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: Steve Strublic <SStrublic@Hypercom.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] link loss/detection at runtime
Date: Tue, 26 Jul 2005 17:44:00 -0000	[thread overview]
Message-ID: <42E6771D.3060306@carallon.com> (raw)
In-Reply-To: <OF4F92EF36.0B5FDD1F-ON0725704A.005B9A03-0725704A.005BC6D9@hypercom.com>

Thanks Steve.

Thats exactly where I had just got to, can't see a better way of doing it.

Could you give an example of what's in your pfn_proc_link_status. I am 
assuming I can copy code snippets out of the dhcp code to work out how 
to bring the interface up and down.

Cheers,

Will

Steve Strublic wrote:
> 
> 
> 
> We had a similar issue at my company.  We ended up hooking FEC_ETH_PHY_INT, writing an ISR/DSR
> combination, and running a thread to allow calls to phy_read().  In the thread, we read the contents
> of the link status register when notified by the DSR that the status has changed.  This also allowed
> us to have multiple notifiers execute upon link status change.
> 
> Something like:
> 
> phy_ok = phy_read(PHY_BMSR2, FEC_ETH_PHY, &mii_reg17);
> 
> if (mii_reg17 & PHY_BMSR2_LINK)
>       link_up_status=true;
> else
>       link_up_status=false;
> 
> (pfn_proc_link_status)(link_up_status) ;
> 
> There may be (probably is) an easier solution, but this one worked for us.
> 
> HTH,
> 
> Steve
> 
> --------
> 
> "A chicken doesn't stop scratching just because the worms are scarce." - Grandma Soderquist's
> Conclusion
> 
> 
> 
>                                                                                                     
>              will_wagner@carallon.com                                                               
>              Sent by:                                                                               
>              ecos-discuss-owner@ecos.sou                                                         To 
>              rceware.org                         ecos-discuss@ecos.sourceware.org                   
>                                                                                                  cc 
>                                                                                                     
>              07/26/2005 05:07 AM                                                            Subject 
>                                                  [ECOS] link loss/detection at runtime              
>                                                                                                     
>                                                                                                     
>                                                                                                     
>                                                                                                     
>                                                                                                     
>                                                                                                     
> 
> 
> 
> 
> Hi All,
> 
> Are there any examples of ethernet drivers that cope with link
> loss/detection after the drivers have been initialised? I am using an
> MPC860 with AMD PHY. I have hunted through the source but can't find any
> examples of this.
> 
> If not can anyone point me to what needs to be done in the bsd stack to
> bring an interface up/down following a change in link status.
> 
> Thanks,
> 
> Will
> 
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
> 


-- 
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:[~2005-07-26 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 12:04 Will Wagner
2005-07-26 16:42 ` Steve Strublic
2005-07-26 17:44   ` Will Wagner [this message]

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=42E6771D.3060306@carallon.com \
    --to=will_wagner@carallon.com \
    --cc=SStrublic@Hypercom.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).