public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Dylan Griffiths <Dylan_G@bigfoot.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Still some problems with UHCI driver in 2.4.5 on VIA chipsets
Date: Fri, 22 Jun 2001 14:55:53 -0400	[thread overview]
Message-ID: <20010622145553.W3715@sventech.com> (raw)
In-Reply-To: <3B2D446A.5C2AEEAC@bigfoot.com> <20010617200855.R9465@sventech.com> <3B2FBF76.40993998@bigfoot.com>
In-Reply-To: <3B2FBF76.40993998@bigfoot.com>; from Dylan_G@bigfoot.com on Tue, Jun 19, 2001 at 03:09:10PM -0600

On Tue, Jun 19, 2001, Dylan Griffiths <Dylan_G@bigfoot.com> wrote:
> Johannes Erdfelt wrote:
> > Could you load uhci with the debug=1 option?
> 
> I did an 'insmod uhci.o debug=1' but the dmesg output did not alter.
> 
> My easy steps to reproduce it is to 'delete selected images' in gphoto such
> that there will be no images in the camera left when the operation is done. 
> At loast it doesn't lock up the camera like it used to :-/
> 
> I think this may be a problem in the dc2xx.o then, since uhci didn't reveal
> any new messages.

It's possible. Many cameras are touchy wrt to the commands it receives.
If one is slightly wrong, some of them will just stop talking.

Did you try with the usb-uhci driver as well?

JE


  reply	other threads:[~2001-06-22 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17 23:59 Still some problems with UHCI driver in 2.4.5 on VIA chipsets Dylan Griffiths
2001-06-18  0:08 ` Johannes Erdfelt
2001-06-19 21:09   ` Dylan Griffiths
2001-06-22 18:55     ` Johannes Erdfelt [this message]
2001-06-22 23:08       ` Dylan Griffiths
2001-06-25 10:48     ` Still some problems with UHCI driver in 2.4.5 on VIA chipsets (Mustek scanner) Catalin BOIE

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=20010622145553.W3715@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=Dylan_G@bigfoot.com \
    --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