mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Gustavo Guillermo Pérez" <gustavo@compunauta.com>,
	linux-usb-devel@lists.sourceforge.net,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: /dev/sr0 not ready, but working
Date: Tue, 22 Nov 2005 14:00:05 -0500	[thread overview]
Message-ID: <20051122190005.GC6592@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0511221349360.21136-100000@iolanthe.rowland.org>

On Tue, Nov 22, 2005 at 01:56:39PM -0500, Alan Stern wrote:
> I know practically nothing about how your device works, so this is just a
> guess.  It seems likely that the IEEE1394-USB/ATA interface controller
> translates the commands it receives over the external bus into a sequence
> of ATA or ATAPI commands that is somewhat different from the sequence of
> commands Linux would use if the drive were directly attached to an IDE
> controller.  As a result, perhaps the drive sends those "not ready"  
> replies when you use it over an external bus but not when you use attach
> it over ATA.
> 
> Or maybe not...  Maybe the drive _does_ send those "not ready" messages 
> and the IDE driver ignores them instead of printing them in the system 
> log.  Or perhaps those messages are sent by the bus interface controller 
> and not by the drive itself.  I just don't know.

The difference is between ide-cd.c and sr.c, most likely.

	Jeff




  reply	other threads:[~2005-11-22 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 22:00 Gustavo Guillermo Pérez
2005-11-21 23:25 ` Jeff Garzik
2005-11-22 15:36   ` [linux-usb-devel] " Alan Stern
2005-11-22 17:43     ` Gustavo Guillermo Pérez
2005-11-22 18:56       ` Alan Stern
2005-11-22 19:00         ` Jeff Garzik [this message]
2005-11-24 15:03           ` Mark Lord
2005-11-24 17:28             ` Alan Stern
2005-11-23  2:21         ` Gustavo Guillermo Pérez
2005-11-22 18:59     ` Jeff Garzik

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=20051122190005.GC6592@havoc.gtf.org \
    --to=jgarzik@pobox.com \
    --cc=gustavo@compunauta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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®