From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IEEE-1394 and disks
Date: Thu, 20 Jan 2005 13:23:47 -0700 [thread overview]
Message-ID: <1106252627.3413.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1106250812.3413.10.camel@localhost.localdomain>
By bridge chips I mean IEEE-1394 to IDE. Also, is it possible to set
spin down time for these IDE disks through 1394? i.e. if they are
inactive for 1 hour, I would like them to spin down. Is this possible?
Trever
On Thu, 2005-01-20 at 12:53 -0700, Trever L. Adams wrote:
> I have a few questions: How stable is firewire (running at 800Mbps or
> faster, if any is available yet)? How stable is the Linux subsystem,
> especially for firewire disks? Is there any particularly 800Mbps bridge
> chips that should be avoided or used?
>
> How stable is the subsystem when the chain is nearly full (62 devices is
> full right?)
>
> How many controllers may be in the system before the Firewire subsystem
> gets confused?
>
> Trever Adams
> --
> "There are two ways to live your life. One is as though nothing is a
> miracle. The other is as though everything is a miracle." -- Albert
> Einstein
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
"If there was strife and contention in the home, very little else in
life could compensate for it." -- Lawana Blackwell, The Courtship of the
Vicar's Daughter, 1998
next prev parent reply other threads:[~2005-01-20 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 19:53 Trever L. Adams
2005-01-20 20:23 ` Trever L. Adams [this message]
2005-02-14 23:49 ` Jody McIntyre
2005-01-26 23:08 ` Jody McIntyre
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=1106252627.3413.12.camel@localhost.localdomain \
--to=tadams-lists@myrealbox.com \
--cc=linux-kernel@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
Powered by JetHome