public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Frank Borich <Frank_Borich@us.xyratex.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: read capacity 16
Date: Thu, 9 Dec 2004 15:02:09 +0000	[thread overview]
Message-ID: <20041209150209.GA16698@infradead.org> (raw)
In-Reply-To: <47F3C2BE74738E4683574107469DFA206783D7@XYUSEX01.xyus.xyratex.com>

On Thu, Dec 09, 2004 at 06:33:15AM -0800, Frank Borich wrote:
> This works as expected using SGI's 2.6.5-rc3-mm4 on ia64 and on Windows
> server 2003 SP1 (still a beta).
> Does anyone know how to get kernels > than 2.4.19 to work ?
> 
> I tried setting max_cmd_len to 16 in hosts.c, but it doesn't change
> anything.

The 2.4 scsi layer doesn't issue 16 byte commands at all. 


  reply	other threads:[~2004-12-09 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 14:33 read capacity 16 Frank Borich
2004-12-09 15:02 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-17 17:20 READ CAPACITY 16 bburk
2008-12-17 17:25 ` Matthew Wilcox
2008-12-17 16:42 Matthew Wilcox
2008-12-17 17:50 ` Grant Grundler
2008-12-17 18:06   ` Matthew Wilcox
2008-12-17 18:57     ` Grant Grundler
2008-12-17 19:04     ` James Bottomley
2008-12-17 19:11       ` Matthew Wilcox
2008-12-17 19:14         ` James Bottomley
2008-12-17 19:32           ` Matthew Wilcox
2008-12-17 19:36             ` James Bottomley
2008-12-17 19:49               ` Matthew Wilcox
2008-12-18  9:05     ` Boaz Harrosh
2008-12-18 14:08       ` Matthew Wilcox
2008-12-18 14:38         ` Boaz Harrosh
2008-12-18 14:49           ` Matthew Wilcox
2008-12-18 14:52           ` James Bottomley
2008-12-18 14:59             ` Boaz Harrosh
2008-12-18 20:41 ` Douglas Gilbert
2004-12-08 21:07 read capacity 16 Frank Borich

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=20041209150209.GA16698@infradead.org \
    --to=hch@infradead.org \
    --cc=Frank_Borich@us.xyratex.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