From: Brad Hards <bhards@bigpond.net.au>
To: Reg Clemens <reg@dwf.com>, linux-kernel@vger.kernel.org
Subject: Re: Dont understand hdc=ide-scsi behaviour.
Date: Fri, 20 Sep 2002 16:46:00 +1000 [thread overview]
Message-ID: <200209201646.00202.bhards@bigpond.net.au> (raw)
In-Reply-To: <200209192108.g8JL8iT6010419@orion.dwf.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 20 Sep 2002 07:08, Reg Clemens wrote:
> I dont understand the behaviour of kernel 2.4.18 (and probably all others)
> when I put the line
> hdc=ide-scsi
> on the load line.
>
> I would EXPECT to get the ide-scsi driver for hdc (my cdwriter) but instead
> get it for BOTH hdc and hdd, the cdwriter and the zip drive.
>
> After starting this way (with hdc=ide-scsi), I find that
> /dev/cdrom2 -> /dev/scd0
> and that to access the zip drive I have to use /dev/sda1 (or /dev/sda4)
There are two slightly different things happening, I think.
1. When you say hdc=ide-scsi, you are telling the IDE system that you don't
want to use the normal IDE interfaces to userland (such as ide-cdrom), but
instead want all access to this device to be accessed through the SCSI
midlayer (and associated SCSI interfaces, like the sg and scd drivers). So
ide-scsi becomes the driver, instead of ide-cdrom. You should be able to see
this in /proc/ide/hdc/driver
2. ide-scsi is greedy, and will grab any IDE device without a driver. ATAPI
floppy devices (hopefully) like your zip drive need the IDE floppy device
driver, which is probably not loaded. What does CONFIG_BLK_DEV_IDEFLOPPY
equal in your kernel config?
> I would EXPECT to get to them via /dev/hdd1 or /dev/hdd4.
And you will, with the right driver loaded :-)
> Did I miss something or is this a bug????
If you load ide-floppy before ide-scsi, and it still doesn't work, then there
is a bug.
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9isQoW6pHgIdAuOMRAtfvAJ9QxzwAyyaLFRIHisEiZ9oEzGm9ngCfZMHB
X/OxH0BykeRSrQKAKj22u2Y=
=E/AW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-20 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 21:08 Reg Clemens
2002-09-20 0:04 ` Allan Duncan
2002-09-20 5:51 ` Andre Hedrick
2002-09-20 6:46 ` Brad Hards [this message]
2002-09-20 14:46 ` Miles Lane
2002-09-20 7:59 ` Brad Hards
2002-09-20 18:44 ` Paul Bristow
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=200209201646.00202.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@dwf.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
all inboxes | Powered by JetHome®