mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Martin Mokrejs <mmokrejs@ribosome.natur.cuni.cz>
Cc: Jay Fenlason <fenlason@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux1394-devel@lists.sourceforge.net
Subject: Re: 2.6.35-rc6 to 2.6.32.16: JuJu firewire issues
Date: Sat, 24 Jul 2010 14:18:10 +0200	[thread overview]
Message-ID: <4C4ADA02.1050704@s5r6.in-berlin.de> (raw)
In-Reply-To: <4C4AD65D.5090008@ribosome.natur.cuni.cz>

Martin Mokrejs wrote:
>   I tried in the morning to connect the IcyBox to this laptops internal
> Ricoh Co Ltd R5C552 IEEE 1394 Controller but had issues to power-up the drive
> at all. Not even using USB hub to supply power to it. I connected it to
> the ricoh chip via a 6 to 4 pin cable but also tried the not very good
> Kouwell 7004 PCMCIA card (which does not supply enough power unless I
> buy external, optional power supply of unknown specs and plug it into the
> PCMCIA card).

FireWire CardBus cards do not (or more precisely, must not) provide bus
power at all, unless if they have a power input port and a fitting PSU
is connected to it.  If a CardBus card puts power onto the FireWire bus
without any extra PSU connected, then this card is miswired and not spec
compliant.  A FireWire bus power provider is required to be able to
deliver 1.5 A current or more, at 8 V or more.  That can't be done via
CardBus.

4-pin FireWire ports OTOH do not provide bus power of course; they lack
the respective pins.

Some FireWire disk enclosures can optionally be powered via USB, but we
all know how unreliable USB bus power is.  Prefer either a dedicated PSU
or regular FireWire bus power.
-- 
Stefan Richter
-=====-==-=- -=== ==---
http://arcgraph.de/sr/

      reply	other threads:[~2010-07-24 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 14:09 Martin Mokrejs
     [not found] ` <20100723180807.GA32319@redhat.com>
2010-07-23 18:38   ` Martin Mokrejs
     [not found]     ` <20100723192646.GB32319@redhat.com>
2010-07-23 20:19       ` Martin Mokrejs
2010-07-23 21:42         ` Stefan Richter
2010-07-23 21:50           ` Stefan Richter
2010-07-23 21:19     ` Stefan Richter
2010-07-24  8:01       ` Stefan Richter
2010-07-24 12:02         ` Martin Mokrejs
2010-07-24 12:18           ` Stefan Richter [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=4C4ADA02.1050704@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=fenlason@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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

all inboxes | Powered by JetHome®