public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Matthew Wilcox <willy@debian.org>
Cc: Anton Blanchard <anton@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Patrick Mochel <mochel@osdl.org>
Subject: Re: pci_domain_nr vs. /sys/devices
Date: Tue, 17 Jun 2003 20:39:29 +0200	[thread overview]
Message-ID: <20030617183929.GA15886@suse.de> (raw)
In-Reply-To: <20030617162546.GS30843@parcelfarce.linux.theplanet.co.uk>

 On Tue, Jun 17, Matthew Wilcox wrote:

> ./drivers/net/3c59x.c:                  strcpy(info.bus_info, VORTEX_PCI(vp)->slot_name);

that one is for ethtool ioctl.
Is 'ethtool -i' obsolete in 2.6?
It seems sysfs has every info already.

olaf@smirnow:~/linux-2.5.72> l /sys/class/net/eth0/
total 0
drwxr-xr-x    3 root     root            0 Jun 17 13:14 ./
drwxr-xr-x    4 root     root            0 Jun 17 13:14 ../
-r--r--r--    1 root     root         4096 Jun 17 13:14 addr_len
-r--r--r--    1 root     root         4096 Jun 17 13:14 address
-r--r--r--    1 root     root         4096 Jun 17 13:14 broadcast
lrwxrwxrwx    1 root     root           34 Jun 17 13:14 device -> ../../../devices/pci0/0000:00:0a.0/
lrwxrwxrwx    1 root     root           30 Jun 17 13:14 driver -> ../../../bus/pci/drivers/3c59x/
-r--r--r--    1 root     root         4096 Jun 17 13:14 features
-rw-r--r--    1 root     root         4096 Jun 17 13:14 flags
-r--r--r--    1 root     root         4096 Jun 17 13:14 ifindex
-r--r--r--    1 root     root         4096 Jun 17 13:14 iflink
-rw-r--r--    1 root     root         4096 Jun 17 13:14 mtu
drwxr-xr-x    2 root     root            0 Jun 17 13:14 statistics/
-rw-r--r--    1 root     root         4096 Jun 17 13:14 tx_queue_len
-r--r--r--    1 root     root         4096 Jun 17 13:14 type

driver, businfo.
drivers/<foo> does not provide a version string.
Should there be an entry for that?

-- 
USB is for mice, FireWire is for men!

  reply	other threads:[~2003-06-17 18:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 14:30 pci_domain_nr vs. /sys/devices Benjamin Herrenschmidt
2003-06-11 14:48 ` Matthew Wilcox
2003-06-11 15:06   ` Benjamin Herrenschmidt
2003-06-11 15:12     ` Matthew Wilcox
2003-06-11 15:40   ` Russell King
2003-06-11 16:00     ` Benjamin Herrenschmidt
2003-06-17  4:52       ` Anton Blanchard
2003-06-11 17:03   ` Patrick Mochel
2003-06-17  4:49   ` Anton Blanchard
2003-06-17  9:41     ` Ivan Kokshaysky
2003-06-17 12:49       ` Anton Blanchard
2003-06-17 13:11         ` Ivan Kokshaysky
2003-06-17 19:42           ` Matthew Wilcox
2003-06-17 21:30             ` Ivan Kokshaysky
2003-06-18 13:02               ` Matthew Wilcox
2003-06-18 13:24                 ` Ivan Kokshaysky
2003-06-17 13:55     ` Matthew Wilcox
2003-06-17 16:25     ` Matthew Wilcox
2003-06-17 18:39       ` Olaf Hering [this message]
2003-06-11 15:42 ` Russell King
2003-06-12  0:37 ` Anton Blanchard
2003-06-12 13:27   ` Benjamin Herrenschmidt

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=20030617183929.GA15886@suse.de \
    --to=olh@suse.de \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=willy@debian.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