mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Michael Brade <brade@informatik.uni-muenchen.de>
Cc: "John Stoffel" <john@stoffel.org>, linux-kernel@vger.kernel.org
Subject: Re: ieee1394: sbp2: sbp2util_node_write_no_wait failed
Date: Mon, 24 Oct 2005 15:48:37 -0400	[thread overview]
Message-ID: <17245.14997.891283.954480@smtp.charter.net> (raw)
In-Reply-To: <200510241834.03948.brade@informatik.uni-muenchen.de>

>>>>> "Michael" == Michael Brade <brade@informatik.uni-muenchen.de> writes:

>> One thing I suggest right off the bat is to make sure that firmware on
>> your external enclosure is updated to the latest/greatest.  Alot of
>> vendors (esp those using the Prolific chipset) don't get it right
>> initially.

Michael> Good guess and damn, yes, I've got the Icy Box IB-351-UE
Michael> which has the prolific chipset, I guess it's the (cursed)
Michael> PL3507. [The IcyBox FAQ says: IB-350/351/360UE Prolific
Michael> (PL3507) - Agere (FW8028)]

I've got the same box, and I've given up on the firewire side of
things and I just use the USB port now.  But it's just my backup box,
so I don't really use it too much.  

Michael> However, I've read that they had problems in 2004 and that
Michael> all new devices (starting from October 2004) have the updated
Michael> firmware already.

Check anyway... I think I posted recently about my luck in getting the
USB side working with 2.6.12+ once I updated the firmware on the
chipset, which was a pain.  

Michael> I have also found some of your posts from 2004 on lkml about
Michael> the prolific chipset, actually anything I found is mostly
Michael> from 2004 :-/

Yeah, from what I've been reading, the Prolific chipset sucked even
for Windows users, at least until the latest firmware.  Goto these
pages:

	http://tech.prolific.com.tw/visitor/v_filebrw_result.asp
	http://forum.rpc1.org/viewtopic.php?t=25140&postdays=0&postorder=asc&&start=25&sid=6801466c15ef74f35a490bbdb423cf37

The second one is a forum which had some useful info.

Michael> So sorry for the dumb question, but do I check if I've got
Michael> the newest firmware without windows? I had a look at
Michael> www.icybox.de but found no firmware for ib-351, only for
Michael> ib-350 and that one is from Dec 2004.

You need to go by chipset, not by enclosure.  I poked on my system,
but there's nothing obvious about how to get the firmware level in the
output of 'lsusb'.  Sorry.

Michael> And even if I've got the newest firmware already, does the
Michael> prolific stuff work by now or should I chuck it out the
Michael> window?

It works with USB, I don't know about firewire since I've just chucked
that for now.  Which is why I got the dual input setup, USB/Firewire.
Haven't tried the firewire on a Windows box either since the upgrade,
might one of these days, but I'm in no rush.

John

  reply	other threads:[~2005-10-24 19:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 12:51 Michael Brade
2005-10-24 14:03 ` John Stoffel
2005-10-24 16:33   ` Michael Brade
2005-10-24 19:48     ` John Stoffel [this message]
2005-10-24 20:23       ` Michael Brade
2005-10-25 11:52       ` Michael Brade
2005-10-31 18:52       ` Michael Brade

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=17245.14997.891283.954480@smtp.charter.net \
    --to=john@stoffel.org \
    --cc=brade@informatik.uni-muenchen.de \
    --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

all inboxes | Powered by JetHome®