From: Luben Tuikov <tluben@rogers.com>
To: Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: [RFC] device identification, VPD 0x83
Date: Thu, 08 May 2003 15:32:32 -0400 [thread overview]
Message-ID: <3EBAB0D0.40807@rogers.com> (raw)
What is the alternative to providing a device identification
if the device doesn't provide one (assuming scanning from
userspace)?
My thoughts are that since device identification is
a property of the device, it should be provided by the
kernel if the device supports it (VPD 0x83 is mandatory).
The reason is security and configuration.
A LLDD can always filter or emulate it (depending on the
bus it's using, e.g. USB Storage) if the device itself
doesn't provide it.
Comments?
--
Luben
reply other threads:[~2003-05-08 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EBAB0D0.40807@rogers.com \
--to=tluben@rogers.com \
--cc=linux-scsi@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