public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 2.6.0-test9: scsi_dev_flags
Date: Sat, 1 Nov 2003 13:13:09 +0000	[thread overview]
Message-ID: <20031101131309.A31429@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031026083850.A15515@beaverton.ibm.com>; from patmans@us.ibm.com on Sun, Oct 26, 2003 at 08:38:50AM -0800

On Sun, Oct 26, 2003 at 08:38:50AM -0800, Patrick Mansfield wrote:
> On Sun, Oct 26, 2003 at 02:47:41PM +0000, Russell King wrote:
> 
> > So, I then tried doing exactly that:
> > 
> > 	scsi_dev_flags=SyQuest:SQ3270S:4096
> 
> If that is the kernel boot line, you need to prefix the argument with
> scsi_mod., i.e. scsi_mod.scsi_dev_flags=, per the module_param
> interface(s).
> 
> > An additional question comes out from this - if quirk information is now
> > to be passed on the kernel command line, how are users supposed to work
> > out the correct command line argument to give for their quirky hardware
> > given that it doesn't appear to be as trivial as the code suggests?
> > (IOW, the scsi_dev_flags option appears to be rather undocumented!)
> 
> There is a bit in Documentation/kernel-parameters.txt, but there should be
> more documentation added somewhere. Also the integer value can be hex
> (0x1000).

Ok, I've tried scsi_mod.scsi_dev_flags= and the kernel whinges:

Unknown boot option `scsi_mod.scsi_dev_flags=SyQuest:SQ3270S:4096': ignoring

and it still wants to spin up the drive (I ended up allowing it during
the first spinup attempt):

sda: Spinning up disk...................ready
SCSI device sda: 524288 512-byte hdwr sectors (268 MB)
sda: Write Protect is off
sda: Mode Sense: 99 00 00 08
SCSI device sda: drive cache: write back
 sda: sda1 sda2
Attached scsi removable disk sda at scsi0, channel 0, id 2, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0,  type 1
Attached scsi generic sg1 at scsi0, channel 0, id 2, lun 0,  type 0

Note that unlike my recent mail to linux-scsi, this time it didn't try
to add the same partitions multiple times.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2003-11-01 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 14:47 2.6.0-test9: scsi_dev_flags Russell King
2003-10-26 16:38 ` Patrick Mansfield
2003-11-01 13:13   ` Russell King [this message]
2003-11-01 17:11     ` 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=20031101131309.A31429@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox