mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Valdis.Kletnieks@vt.edu
Cc: Miroslaw Mieszczak <mieszcz@zabrze.zigzag.pl>,
	jgarzik@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: Patch for link detection for R8169
Date: Tue, 6 Sep 2005 23:15:51 +0200	[thread overview]
Message-ID: <20050906211551.GC20862@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200509062059.j86Kx17K022141@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> :
> On Tue, 06 Sep 2005 22:42:21 +0200, Francois Romieu said:
> 
> > Currently one can do 'ifconfig ethX up', check the link status, then try
> > to DHCP or whatever. Apparently a few drivers do not support tne detection
> > of link as presented above. So is it anything like a vendor requirement/a
> > standard (or should it be the new right way (TM)) or does the userspace
> > needs fixing wrt its expectation ?
> 
> The "ifconfig up then check link status" method is probably usable for the
> vast majority of cases.  Are there any driver/card combos that *can't* be
> fixed to support that?  (A somewhat hidden side effect is that if you're

I meant "as presented above" == "check the link while the network device
is down".

--
Ueimor

  reply	other threads:[~2005-09-06 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 14:32 Miroslaw Mieszczak
2005-09-06 14:46 ` Matthieu CASTET
2005-09-06 19:46 ` Francois Romieu
2005-09-06 20:02   ` Valdis.Kletnieks
2005-09-06 20:42     ` Francois Romieu
2005-09-06 20:59       ` Valdis.Kletnieks
2005-09-06 21:15         ` Francois Romieu [this message]
2005-09-07 14:45       ` Miroslaw Mieszczak
2005-09-07 18:17         ` Francois Romieu
     [not found]           ` <43207052.3030403@zabrze.zigzag.pl>
2005-09-08 23:49             ` Francois Romieu
2005-09-07  1:56   ` Jeff Garzik

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=20050906211551.GC20862@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mieszcz@zabrze.zigzag.pl \
    /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

all inboxes | Powered by JetHome®