From: "Martin Schwenke" <martin@meltin.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andries Brouwer <aebr@win.tue.nl>, Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: [PATCH] /proc/scsi/map
Date: Fri, 21 Jun 2002 08:59:19 +1000 [thread overview]
Message-ID: <200206202259.IAA01298@thucydides.inspired.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0206201046340.8225-100000@home.transmeta.com>
>>>>> "Linus" == Linus Torvalds <torvalds@transmeta.com> writes:
Linus> But driverfs also gives information that /sbin/hotplug doesn't:
Linus> [...]
Linus> In other words, it's just a way of exposing information
Linus> that the kernel already has, and that the kernel has to
Linus> have _anyway_.
Does it have to be limited ot information that the kernel already has?
In particular, I'm thinking of the SCSI standard inquiry and EVPD
inquiry pages. Mike Sullivan's patch does some SCSI inquiries and
extracts information from the results. I'm wondering if the SCSI
driver could just do all of the available EVPD inquiries (available
pages are listed in the TOC on EVPD inquiry page 0), and use driverfs
to expose all of that (binary) information.
Right now the inquiries can be done from userspace using an ioctl().
peace & happiness,
martin
next prev parent reply other threads:[~2002-06-20 23:00 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 0:44 Kurt Garloff
2002-06-20 5:03 ` Linus Torvalds
2002-06-20 7:09 ` Martin Schwenke
2002-06-20 15:13 ` Linus Torvalds
2002-06-20 15:36 ` Dave Jones
2002-06-20 17:01 ` Linus Torvalds
2002-06-20 16:55 ` Andries Brouwer
2002-06-20 17:52 ` Patrick Mansfield
2002-06-20 18:36 ` Linus Torvalds
2002-06-20 18:52 ` James Bottomley
2002-06-20 19:15 ` Linus Torvalds
2002-06-20 16:28 ` Benjamin Herrenschmidt
2002-06-21 0:46 ` Linus Torvalds
2002-06-20 16:49 ` Benjamin Herrenschmidt
2002-06-20 20:06 ` Oliver Xymoron
2002-06-22 18:27 ` Pavel Machek
2002-06-20 18:11 ` Linus Torvalds
2002-06-20 22:59 ` Martin Schwenke [this message]
2002-06-20 23:13 ` Linus Torvalds
2002-06-22 18:25 ` Pavel Machek
2002-06-26 16:03 ` Ihno Krumreich
2002-07-01 17:33 ` Patrick Mochel
2002-06-20 19:55 ` Greg KH
2002-06-20 19:18 ` Patrick Mochel
2002-06-21 6:28 ` Mike Touloumtzis
2002-06-20 11:25 ` Kurt Garloff
2002-06-20 15:34 ` Linus Torvalds
2002-06-20 16:30 ` Martin Dalecki
2002-06-20 16:58 ` James Bottomley
2002-06-20 18:27 ` Linus Torvalds
2002-06-20 20:55 ` Martin Dalecki
2002-06-20 21:04 ` Linus Torvalds
2002-06-20 21:36 ` Martin Dalecki
2002-06-20 20:12 ` Patrick Mochel
2002-06-20 22:29 ` Martin Dalecki
2002-06-22 18:42 ` Pavel Machek
2002-06-21 14:29 ` sullivan
2002-06-21 16:17 ` Patrick Mochel
2002-06-21 21:33 ` Oliver Xymoron
2002-06-22 4:38 ` Nick Bellinger
2002-06-22 19:41 ` Douglas Gilbert
2002-06-22 19:11 ` Nick Bellinger
2002-06-25 18:13 ` Patrick Mochel
2002-06-25 16:05 ` Patrick Mochel
2002-06-25 16:57 ` Oliver Xymoron
2002-06-25 18:58 ` Patrick Mochel
2002-07-03 1:01 ` Pavel Machek
2002-06-20 18:32 ` Kurt Garloff
2002-06-20 18:53 ` Linus Torvalds
2002-06-21 9:07 ` Kurt Garloff
2002-06-20 23:59 Grover, Andrew
2002-06-22 6:29 Adam J. Richter
2002-06-25 16:17 ` Patrick Mochel
2002-06-22 17:24 David Brownell
2002-06-22 17:48 ` Roman Zippel
2002-06-22 20:11 ` Douglas Gilbert
2002-06-22 20:57 ` Roman Zippel
2002-06-22 18:18 ` Nick Bellinger
2002-06-24 1:50 ` David Brownell
2002-06-25 16:46 ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 17:49 ` David Brownell
2002-06-26 23:39 ` Nick Bellinger
2002-07-01 17:45 ` Patrick Mochel
2002-07-03 0:59 ` Pavel Machek
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=200206202259.IAA01298@thucydides.inspired.net.au \
--to=martin@meltin.net \
--cc=aebr@win.tue.nl \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
/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®