From: Douglas Gilbert <dougg@torque.net>
To: Andries.Brouwer@cwi.nl
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
mdharm-scsi@one-eyed-alien.net, patmans@us.ibm.com
Subject: Re: [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code
Date: Mon, 05 May 2003 17:58:28 +1000 [thread overview]
Message-ID: <3EB619A4.5090407@torque.net> (raw)
In-Reply-To: <UTC200304250047.h3P0lhl03517.aeb@smtp.cwi.nl>
Andries.Brouwer@cwi.nl wrote:
>>Remove the scsi EVPD code.
>
>
> Good! That simplifies many things.
Good?? Just because there are millions of brain damaged
devices that can't implement rule 0 of a protocol,
Patrick removes one of the best features added to
the scsi subsystem in the 2.5 development series.
Patrick's patch is now in lk 2.5.69 .
So we are back to all the fun games of opening/
querying/closing likely looking device nodes in
the /dev space (and I speak from experience).
What a joy.
Surely there is a better way. Why not do the VPD=0x83
query on devices that claim to be SCSI-3 compliant
or better. The scsi mid level driver (and/or the
usb-storage + sbp2 LLDs) could have a sysfs parameter
such as "simple_scan". The filters discussion
showed more promise than this blunt approach.
I have contemplated putting the VPD=0x83 code in
lsscsi but it won't be pretty (e.g. requiring root
privilege, side effects including locking up
certain USB storage devices :-) ).
Doug Gilbert
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2003-05-05 7:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 0:47 [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code Andries.Brouwer
2003-05-05 7:58 ` Douglas Gilbert [this message]
2003-05-05 14:17 ` James Bottomley
2003-05-05 15:52 ` Mike Anderson
2003-05-05 16:14 ` James Bottomley
2003-05-05 16:26 ` Patrick Mansfield
2003-05-05 16:57 ` Mike Anderson
2003-05-05 17:01 ` James Bottomley
2003-05-05 16:38 ` Patrick Mansfield
2003-05-05 16:59 ` James Bottomley
2003-05-05 17:46 ` Mike Anderson
2003-05-05 22:51 ` Patrick Mansfield
2003-05-06 1:39 ` Douglas Gilbert
2003-05-06 4:11 ` Patrick Mansfield
2003-05-06 5:58 ` Douglas Gilbert
2003-05-06 21:11 ` Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 0:22 Patrick Mansfield
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=3EB619A4.5090407@torque.net \
--to=dougg@torque.net \
--cc=Andries.Brouwer@cwi.nl \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.