From: Andre Bonin <kernel@bonin.ca>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: root@chaos.analogic.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Firewire Disks. (fwd)
Date: Mon, 10 Jun 2002 14:59:16 -0400 [thread overview]
Message-ID: <3D04F704.5090202@bonin.ca> (raw)
In-Reply-To: <Pine.LNX.3.95.1020610141042.17451B-100000@chaos.analogic.com> <3D04EDC1.8010402@drugphish.ch>
Roberto Nibali wrote:
> Hi,
>
>> 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?
next prev parent reply other threads:[~2002-06-10 18:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 0:20 Douglas Gilbert
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=3D04F704.5090202@bonin.ca \
--to=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
--cc=root@chaos.analogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.