From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: David Hollis <dhollis@davehollis.com>,
Auke Kok <auke-jan.h.kok@intel.com>,
dean gaudet <dean@arctic.org>, Jeff Garzik <jgarzik@pobox.com>,
dhinds@pcmcia.sourceforge.org, netdev@vger.kernel.org
Subject: Re: mii-tool gigabit support.
Date: Fri, 29 Sep 2006 10:54:54 -0700 [thread overview]
Message-ID: <451D5DEE.2080609@hp.com> (raw)
In-Reply-To: <20060929101215.649a9e32@freekitty>
2) develop some style
>>of register description definition type of text file, maybe XML, maybe
>>INI style or something stored in /etc/ethtool as <drivername>.conf or
>>something like that. This way, ethtool doesn't have to be
>>changed/updated/patched/likely-bug-added for every single device known
>>to man.
>>
>>Just a thought.
>
>
> We could switch to shared libraries like 'tc' uses.
From a practical standpoint is shipping a new config file or a new shared
library all that much different from a new ethtool binary?
rick
next prev parent reply other threads:[~2006-09-29 17:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 21:51 mii-tool gigabit support Stephen Hemminger
2006-09-26 21:55 ` Jeff Garzik
2006-09-26 22:09 ` Stephen Hemminger
2006-09-27 13:00 ` David Acker
2006-09-27 15:00 ` Auke Kok
2006-09-27 16:20 ` Jeff Kirsher
2006-09-27 17:08 ` Rick Jones
2006-09-27 17:50 ` Auke Kok
2006-09-27 17:57 ` Rick Jones
2006-09-27 18:05 ` Maciej W. Rozycki
2006-09-27 18:42 ` Auke Kok
2006-09-28 12:10 ` Maciej W. Rozycki
2006-09-27 20:26 ` David Acker
2006-09-27 19:24 ` dean gaudet
2006-09-27 19:31 ` Stephen Hemminger
2006-09-27 19:32 ` Auke Kok
2006-09-27 19:37 ` dean gaudet
2006-09-29 16:12 ` David Hollis
2006-09-29 17:12 ` Stephen Hemminger
2006-09-29 17:54 ` Rick Jones [this message]
2006-10-01 14:31 ` Michael Tokarev
2006-09-27 19:15 ` dean gaudet
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=451D5DEE.2080609@hp.com \
--to=rick.jones2@hp.com \
--cc=auke-jan.h.kok@intel.com \
--cc=dean@arctic.org \
--cc=dhinds@pcmcia.sourceforge.org \
--cc=dhollis@davehollis.com \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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 NNTP newsgroup(s).