linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: thomas schorpp <t.schorpp@gmx.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Timothy Thelin <Timothy.Thelin@wdc.com>,
	usb-storage@lists.one-eyed-alien.net, linux-ide@vger.kernel.org,
	Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver
Date: Mon, 07 Nov 2005 21:07:10 +0100	[thread overview]
Message-ID: <436FB3EE.1090406@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0511071427580.5078-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Mon, 7 Nov 2005, thomas schorpp wrote:
> 
> 
>>>I don't think blacklisting is a good way to do this.  In principle any USB 
>>>mass storage device -- any SCSI device, in fact -- might have a 
>>>vendor-specific pass-thru needing special handling.
>>
>>no. that would be not industry best practice and uneconomical sw effort.
> 
> 
> Adding vendor-specific codes to SCSI devices isn't industry best practice?  
> I can't argue with that, but it is very common nevertheless.

not for all the cheap noname consumer stuff around. maybe in your scsi-320 server 
world i cant afford.

> 
> Is it an uneconomical software effort?  Ridiculous -- it's not software at 
> all, it's part of the firmware.

i thought were speaking of OS drivers here?

> 
> 
>>remember this devices are mainly "designed for windows" and WHQL certification 
>>is expensive for every single driver. and ms has only one driver for all usb storage 
>>right now, all boxes and sticks i had here use it.
> 
> 
> I think you have a very limited view of how devices are "designed".  
> Besides, I specifically said I was talking about _all_ SCSI devices, not 
> just USB ones.
> 

yes, for the second sentence, this is made clear now.

> 
>>> It doesn't have to be 
>>>correlated with the vendor, the product, the SCSI level, the transport, or 
>>>anything else.
>>
>>yes. the sheet for design recommended cypress chips state all ATACB and ATA-Security.
>>i would be make no sense to implement different behaviuors in chips for the same purpose.
> 
> 
> That's what Cypress does, sure.  But who says that other vendors have to 
> copy Cypress?  For the most part they don't.  Neither does T10.

they dont copy cypress, they want to reduce costs, processes and resulting 
"standards" should be compatible, therefore.

> 
> As for whether it makes no sense -- you have your point of view.  Business 
> people have a very different point of view; to them it might make 
> excellent sense, to help secure a competitive advantage.

:D i'm no business man. i am a generalist and i just want to lock my external hdd.

> 
> Alan Stern
> 
> -

tom schorpp

  reply	other threads:[~2005-11-07 20:07 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 18:30 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver Timothy Thelin
2005-11-04 18:58 ` James Bottomley
2005-11-04 20:30   ` Matthew Dharm
2005-11-04 20:49     ` James Bottomley
2005-11-05 23:55       ` Matthew Dharm
2005-11-06  0:49         ` James Bottomley
2005-11-06  3:38           ` thomas schorpp
2005-11-06 21:58           ` Matthew Dharm
2005-11-06 22:28             ` thomas schorpp
2005-11-06 23:52               ` Patrick Mansfield
2005-11-07 16:59                 ` Matthew Dharm
2005-11-07 17:05                 ` Matthew Dharm
2005-11-07 17:24                   ` Patrick Mansfield
2005-11-07 17:46                     ` Alan Stern
2005-11-07 18:06                       ` thomas schorpp
2005-11-07 19:33                         ` Alan Stern
2005-11-07 20:07                           ` thomas schorpp [this message]
2005-11-07 17:53                     ` Christoph Hellwig
2005-11-07 17:54                     ` thomas schorpp
2005-11-07 18:57                       ` Patrick Mansfield
2005-11-07 19:53                         ` Alan Stern
2005-11-07 20:47                           ` Patrick Mansfield
2005-11-07 20:59                             ` Alan Stern
2005-11-07 22:05                               ` James Bottomley
2005-11-08 17:09                                 ` Alan Stern
2005-11-08 23:05                                   ` Mike Anderson
2005-11-09 15:35                                     ` Alan Stern
2005-12-01 11:35                                 ` [PATCH] writable scsi_level [was: [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver] Douglas Gilbert
2005-11-08 13:51                             ` [usb-storage] [Merging ATA passthru] on integratingSMART/ATA-Security in usb-storage driver Pat LaVarre
2005-11-06 23:15             ` [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security " James Bottomley
2005-11-07 18:14         ` Patrick Mansfield
2005-11-04 23:56     ` Andries Brouwer
2005-11-04 23:46 ` Pete Zaitcev
2005-11-05 16:20   ` thomas schorpp
2005-11-05 18:01     ` [usb-storage] [Merging ATA passthru] on integratingSMART/ATA-Security " Pat LaVarre
  -- strict thread matches above, loose matches on Subject: below --
2005-11-08 19:50 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security " Timothy Thelin
2005-11-09  9:04 ` thomas schorpp
2005-11-09  9:45   ` thomas schorpp
2005-11-09 10:05     ` thomas schorpp
2005-11-09 13:21     ` Mark Lord
2005-11-09 14:05       ` thomas schorpp
2005-11-07 20:18 Timothy Thelin
2005-11-07 17:51 Timothy Thelin
2005-11-02 22:18 Timothy Thelin
2005-11-02 23:22 ` thomas schorpp
2005-11-02 23:45 ` Matthew Dharm
2005-11-04  4:08   ` James Bottomley
2005-11-04 17:28     ` Matthew Dharm
2005-11-04 18:33       ` James Bottomley
2005-11-04 20:30         ` Matthew Dharm
2005-11-04 20:53           ` James Bottomley
2005-11-02 20:33 Timothy Thelin
2005-11-02 21:55 ` thomas schorpp
2005-11-02 14:08 thomas schorpp
2005-11-02 16:05 ` [usb-storage] " Alan Stern
2005-11-02 19:12   ` thomas schorpp
2005-11-02 19:26     ` Alan Stern
2005-11-02 20:41       ` thomas schorpp

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=436FB3EE.1090406@gmx.de \
    --to=t.schorpp@gmx.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Timothy.Thelin@wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.com \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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).