public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Cc: Alan Stern <stern@rowland.harvard.edu>,
	USB Storage list <usb-storage@lists.one-eyed-alien.net>,
	USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] Genesys USB 2.0 enclosures
Date: Sun, 4 Sep 2005 10:46:01 +0200	[thread overview]
Message-ID: <200509041046.01652.lkml@kcore.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509032151040.5675-100000@netrider.rowland.org>

On Sunday 04 September 2005 03:53, Alan Stern wrote:
>
> This one certainly goes into the Bizarro file.
>
> Just out of curiosity -- when you use the powered hub, does the drive work
> even if you remove that delay completely?

I haven't tested that. I will, next time I need the drive, which will probably 
be in about a week. 

I just wanted to make my backup, and finally managed to do that. I don't get 
it either what's really wrong with these chips - but it was one of the 
recommendations i found on the linux-usb device list pages. And it seems to 
work.

If now only I can get the firewire part of one of them working without 
serialize_io, then I can use that too.

Jan

-- 
A billion here, a billion there -- pretty soon it adds up to real money.
		-- Sen. Everett Dirksen, on the U.S. defense budget

  reply	other threads:[~2005-09-04  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0412151627350.2419-100000@ida.rowland.org>
     [not found] ` <200503291344.42951.lkml@kcore.org>
     [not found]   ` <42499406.7090406@ipom.com>
2005-09-03 16:12     ` Genesys USB 2.0 enclosures Jan De Luyck
2005-09-04  1:53       ` [linux-usb-devel] " Alan Stern
2005-09-04  8:46         ` Jan De Luyck [this message]
2005-09-04 21:04         ` Matthew Dharm
2005-09-04 22:10           ` Grant Coady

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=200509041046.01652.lkml@kcore.org \
    --to=lkml@kcore.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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