public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David T Hollis <dhollis@davehollis.com>
To: "David S. Miller" <davem@redhat.com>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: We have ethtool_ops, any thoughts on miitool_ops?
Date: Fri, 29 Aug 2003 07:46:32 -0400	[thread overview]
Message-ID: <3F4F3D18.4010804@davehollis.com> (raw)
In-Reply-To: <20030829041629.69a3be62.davem@redhat.com>

David S. Miller wrote:

>On Fri, 29 Aug 2003 10:50:17 +0200
>Arjan van de Ven <arjanv@redhat.com> wrote:
>
>  
>
>>On Fri, 2003-08-29 at 04:14, David T Hollis wrote:
>>    
>>
>>>If a driver is converted to use ethtool_ops, it does not seem to have 
>>>the ability to support mii-tool any longer.  RedHat uses mii-tool to 
>>>check for link before running dhclient so that you don't have to wait 
>>>forever for dhclient to timeout if the connection is down (laptops, 
>>>etc). 
>>>      
>>>
>>this is legacy; the road to the future for this is ethtool + the link
>>status change notification stuff 
>>    
>>
>
>Besides, the original claim is false.  You can still support all
>the other ioctls however you want, even the MII ones, after
>enabling ethtool_ops in a driver.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>
Thanks for the pointer.  I didn't realize I could still have the old 
ioctl handler and just not worry about the ethool portion of it. 


      reply	other threads:[~2003-08-29 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29  2:14 We have ethtool_ops, any thoughts on miitool_ops? David T Hollis
2003-08-29  8:50 ` Arjan van de Ven
2003-08-29 11:16   ` David S. Miller
2003-08-29 11:46     ` David T Hollis [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=3F4F3D18.4010804@davehollis.com \
    --to=dhollis@davehollis.com \
    --cc=arjanv@redhat.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.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