From: Michael Brade <brade@informatik.uni-muenchen.de>
To: "John Stoffel" <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ieee1394: sbp2: sbp2util_node_write_no_wait failed
Date: Mon, 24 Oct 2005 22:23:37 +0200 [thread overview]
Message-ID: <200510242223.43114.brade@informatik.uni-muenchen.de> (raw)
In-Reply-To: <17245.14997.891283.954480@smtp.charter.net>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Monday 24 October 2005 21:48, John Stoffel wrote:
> 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&&star
>t=25&sid=6801466c15ef74f35a490bbdb423cf37
>
> The second one is a forum which had some useful info.
Thank you so much for your help! It probably won't make my device work with
ieee1394 out of the blue but it sure got me out of my ignorance!
> 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
Ok, I will try that then. I have only USB 1.1 on my laptop so I guess either
I'll get rid of the icy box (what a name..) or get a USB 2.0 PCMCIA card.
Cheers,
--
Michael Brade; KDE Developer, Student of Computer Science
|-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
°--web: http://www.kde.org/people/michaelb.html
KDE 3: The Next Generation in Desktop Experience
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-24 20:22 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
2005-10-24 20:23 ` Michael Brade [this message]
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=200510242223.43114.brade@informatik.uni-muenchen.de \
--to=brade@informatik.uni-muenchen.de \
--cc=john@stoffel.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 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®