public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Keenan <matt.keenan@btinternet.com>
To: Jens Axboe <axboe@suse.de>
Cc: Bill Davidsen <davidsen@tmr.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CD writing - related question
Date: Tue, 07 Feb 2006 09:22:26 +0000	[thread overview]
Message-ID: <43E866D2.4050103@btinternet.com> (raw)
In-Reply-To: <20060202203503.GH4215@suse.de>

Jens Axboe wrote:

>On Mon, Jan 30 2006, Bill Davidsen wrote:
>  
>
>>Please take this as a question to elicit information, not an invitation 
>>for argument.
>>
>>In Linux currently:
>> SCSI - liiks like SCSI
>> USB - looks like SCSI
>> Firewaire - looks like SCSI
>> SATA - looks like SCSI
>>    
>>
>
>SATA will _not_ look like SCSI in the future.
>
>  
>
>> Compact flash and similar - looks like SCSI
>>    
>>
>
>? CF adapters are usually IDE, so looks like ATA.
>
>  
>
>> ATAPI - looks different unless ide-scsi used
>>    
>>
>
>But it's all besides the point, it doesn't matter what the device
>special file looks like (if it's SCSI or not). What matters is that you
>talk to the device the same way - and that way is currently SG_IO.
>
>That a device hangs off the SCSI stack because that is the way the
>author wrote eg usb-storage is irrelevant. What matters is that you open
>the device in question and use SG_IO to talk to it.
>
>Talking about the SCSI stack and ide-scsi completely misses the point.
>
>  
>
Jens,

Is there a document that clearly lists how these components (SCSI, 
SG_IO, ATA/PI etc et al) connect together and what protocol / transports 
they use? I suspect the problem with all these current arguments is that 
very few people understand how this all works / connects. I think alot 
of people equate kconfig options with how the stuff works under the hood 
(even though a number of these config options are badly named to say the 
least).

Matt


  reply	other threads:[~2006-02-07  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 23:30 CD writing - related question Bill Davidsen
2006-02-01 21:04 ` Pavel Machek
2006-02-02 16:49   ` Jan Engelhardt
2006-02-02 19:40   ` Bill Davidsen
2006-02-02 20:19     ` Pavel Machek
2006-02-03  2:36       ` Bill Davidsen
2006-02-02 20:39     ` Jens Axboe
2006-02-02 21:05     ` Krzysztof Halasa
2006-02-02 20:35 ` Jens Axboe
2006-02-07  9:22   ` Matt Keenan [this message]
2006-02-07 11:04     ` Xavier Bestel
2006-02-07 13:47       ` Bill Davidsen
2006-02-07 13:40     ` Jens Axboe

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=43E866D2.4050103@btinternet.com \
    --to=matt.keenan@btinternet.com \
    --cc=axboe@suse.de \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@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