From: Douglas Gilbert <dougg@torque.net>
To: Andre Bonin <kernel@bonin.ca>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Firewire Disks. (fwd)
Date: Mon, 10 Jun 2002 20:20:24 -0400 [thread overview]
Message-ID: <3D054248.84262C73@torque.net> (raw)
Andre Bonin wrote:
>Roberto Nibali wrote:
>>> I know there is support for "firewire" in the kernel. Is there
>>> support for "firewire" disks? If so, how do I enable it?
>>
>>
>> Yes, there is and it is attached to the SCSI layer via the sbp2 driver.
>> You need following set of modules to get it working:
>>
>> scsi_mod, sd_mod, ohci1394, raw1394, ieee1394, sbp2
>
>A lot of caddies that wrap hd's have started coming out and, as you may
>know, USB 2.0 supports 480mbps x-fer rate (ideal). So it's pretty
>intreguing.
>
>Does the SCSI layer via sbp2 provide functionality for USB 2.0 (EHCI)
>disks?
Yes, disks using USB (2.0 or 1.x) and ieee1394 protocols appear
as scsi disks in linux. Prompted by your question, I decided
to check that both are functioning in lk 2.5.21. [ide-scsi is
broken in lk 2.5.21 (worked in 2.5.20) and Martin says a fix is
coming.]
Here are 3 "scsi" disks on my system:
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST318451LW Rev: 0003
Type: Direct-Access ANSI SCSI revision: 03
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: QUANTUM Model: FIREBALL ST3.2A Rev:
Type: Direct-Access ANSI SCSI revision: 06
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: MAXTOR 6 Model: L040J2 Rev: AR1.
Type: Direct-Access ANSI SCSI revision: 02
The Seagate disk is "real" scsi, the Quantum is an old IDE disk
in a ieee1394 enclosure, while the Maxtor is recent ATA disk
in a USB 2.0 enclosure. Here are the modules loaded:
$ lsmod
Module Size Used by
usb-storage 69776 0
ehci-hcd 23600 0 (unused)
sbp2 15536 0 (unused)
ohci1394 18608 0 (unused)
ieee1394 30704 0 [sbp2 ohci1394]
usbcore 65920 1 [usb-storage ehci-hcd]
Both sd_mod and scsi_mod are built into the kernel in my system.
If I use the Maxtor in either enclosure, the streaming bandwidth
is 14 MB/sec which should be more than sufficient for most
purposes.
One interesting development in the lk 2.5 series is driverfs.
It may give us a consistent way to show what is going on here
under the covers. It will also allow user space code to use
various hotplug alerts to load up the required modules without
user intervention. Mike Sullivan's persistent naming patch could
then place the partitions at known device names.
Doug Gilbert
next reply other threads:[~2002-06-11 0:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 0:20 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-10 18:11 Firewire Disks. (fwd) Richard B. Johnson
2002-06-10 18:14 ` Ben Collins
2002-06-10 18:25 ` Richard B. Johnson
2002-06-17 16:46 ` Richard B. Johnson
2002-06-17 17:23 ` Ben Collins
2002-06-10 18:19 ` Roberto Nibali
2002-06-10 18:59 ` Andre Bonin
2002-06-10 19:12 ` Erik Andersen
2002-06-10 19:55 ` Greg KH
2002-06-10 20:12 ` Roberto Nibali
2002-06-13 12:48 ` Richard B. Johnson
2002-06-13 15:36 ` Gerald Britton
2002-06-17 12:51 ` Richard B. Johnson
2002-06-17 16:29 ` Roberto Nibali
2002-06-17 17:12 ` Richard B. Johnson
2002-06-18 13:47 ` Richard B. Johnson
2002-06-18 23:55 ` Roberto Nibali
2002-06-19 13:02 ` Richard B. Johnson
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=3D054248.84262C73@torque.net \
--to=dougg@torque.net \
--cc=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
--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