From: Ed Sweetman <safemode2@comcast.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Bernard Pidoux <pidoux@ccr.jussieu.fr>, linux-kernel@vger.kernel.org
Subject: Re: Why SCSI module needed for PCI-IDE ATA only disks ?
Date: Mon, 04 Dec 2006 20:39:00 -0500 [thread overview]
Message-ID: <4574CDB4.1050704@comcast.net> (raw)
In-Reply-To: <4574B2E4.8060206@garzik.org>
Jeff Garzik wrote:
> Bernard Pidoux wrote:
>> I am asking why need to compile the following modules while I do not
>> have any SCSI device ?
>
> libata uses SCSI to provide a lot of infrastructure that it would
> otherwise have to recreate. Also, using SCSI meant that it
> automatically worked in existing installers.
>
> Jeff
>
This confusion could easily be remedied by explaining the requirement in
the Help output for libata drivers/section. Also, making a dependency
in the menu (since there is one) or automatically selecting the required
scsi items when you select a libata driver would seem logical. As it is,
nothing is said of scsi requirements in menuconfig. Trying to boot a
machine without compiling the scsi drivers (something you're allowed to
do) results in a system that boots and initializes the ata busses but
can't communicate to any of the drives on them, (useless).
Then maybe later down the road, moving those scsi drivers shared by scsi
and libata to the generic block layer would seem logical. That is, when
ide is gone from the kernel and all the kernel speaks is scsi, there
would be no need to differentiate scsi from the generic block layer
devices, and no need to compile "scsi" drivers to have libata driver
support, eliminating any possible further confusion.
next prev parent reply other threads:[~2006-12-05 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 21:27 Why SCSI module needed for PCI-IDE ATA only disks ? Bernard Pidoux
2006-12-04 22:00 ` Phillip Susi
2006-12-04 23:44 ` Jeff Garzik
2006-12-05 1:39 ` Ed Sweetman [this message]
[not found] <fa.juE97gahpb4n2kNNH/Todtcvh3s@ifi.uio.no>
[not found] ` <fa.IqtlZas3d+ZPuhF6S6N/ivdF8Wo@ifi.uio.no>
[not found] ` <fa.HDRhmOhDQliejH7ijqJBWw9Jw0o@ifi.uio.no>
2006-12-06 1:21 ` Robert Hancock
2006-12-06 2:07 ` Ed Sweetman
2006-12-06 2:14 ` Robert Hancock
2006-12-06 2:46 ` Ed Sweetman
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=4574CDB4.1050704@comcast.net \
--to=safemode2@comcast.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
/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