All of lore.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Firewire/sbp2 troubles with Linux 2.6.0
Date: Sun, 21 Dec 2003 20:34:28 +0100	[thread overview]
Message-ID: <yw1xzndm55iz.fsf@ford.guide> (raw)
In-Reply-To: <20031221184840.GR6607@phunnypharm.org> (Ben Collins's message of: 48:40 -0500")

Ben Collins <bcollins@debian.org> writes:

>> > As far as 10mbs, you have to remember that even though firewire is much
>> > higher than that, your drive is still an IDE, and the firewire is still
>> > going through an IDE bridge. So the limitation lies in the IDE bridge.
>> > I've seen performance as high as 34MB/s with good IDE bridges and
>> > drives, though.
>> 
>> The disks will easily do 40 MB/s on a good IDE controller.  It seems
>> like a rather bad bridge to me if it has that much overhead.  I
>> haven't seen many different options for sale, either.
>
> Most things based on newer Oxford chips seem to work pretty well. What
> ohci1394 controller do you have though?

I have this:

00:0a.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 1687
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at e5800000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: <available only to root>

-- 
Måns Rullgård
mru@kth.se

      reply	other threads:[~2003-12-21 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21  3:26 Firewire/sbp2 troubles with Linux 2.6.0 Måns Rullgård
2003-12-21  3:53 ` Ben Collins
2003-12-21 10:42   ` Måns Rullgård
2003-12-21 14:48     ` Ben Collins
2003-12-21 15:58       ` Måns Rullgård
2003-12-21 18:31         ` Ben Collins
2003-12-21 19:09           ` Måns Rullgård
2003-12-21 18:48             ` Ben Collins
2003-12-21 19:34               ` Måns Rullgård [this message]

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=yw1xzndm55iz.fsf@ford.guide \
    --to=mru@kth.se \
    --cc=bcollins@debian.org \
    --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 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.