mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Duncan Sands <baldrick@wanadoo.fr>
To: Dwaine_Garden@wsib.on.ca
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] USB speedtouch: don't open a connection if no firmware
Date: Wed, 9 Apr 2003 10:31:37 +0200	[thread overview]
Message-ID: <200304091031.37302.baldrick@wanadoo.fr> (raw)
In-Reply-To: <OF50785981.C7D592CC-ON85256D02.007454B5-85256D02.007ACB50@wsib.on.ca>

On Tuesday 08 April 2003 23:16, Dwaine_Garden@wsib.on.ca wrote:
> I have noticed with the usbvision code, that when a device like it's own
> is called.  Webcam (Bttv) and the usbvision device.   It take forever to
> load and initialize the driver.
>
> People complain it sometimes it takes two minutes.   At first I thought
> they were making up things.
>
> I have another video and audio capture device.   I only see problem when
> both device have their drivers loaded.
>
> I'm like you.  I'm going to get to removing all the MOD_INC_USE_COUNT;
> code.

Hi Dwaine, I don't understand your email too well, sorry.  Many USB devices
take a while before they are usable, because first you need to load some
firmware into them.  MOD_INC_USE_COUNT will not slow down initialisation.
It is to do with unloading the driver, and stops the driver being unloaded when
it would be dangerous to do so.

All the best,

Duncan.

       reply	other threads:[~2003-04-09  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF50785981.C7D592CC-ON85256D02.007454B5-85256D02.007ACB50@wsib.on.ca>
2003-04-09  8:31 ` Duncan Sands [this message]
2003-04-08  7:26 Duncan Sands
2003-04-08 20:12 ` [linux-usb-devel] " Greg KH
2003-04-08 20:22   ` Duncan Sands
2003-04-08 21:40     ` Greg KH
2003-04-09  8:28       ` Duncan Sands
2003-04-09 23:31         ` Greg KH

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=200304091031.37302.baldrick@wanadoo.fr \
    --to=baldrick@wanadoo.fr \
    --cc=Dwaine_Garden@wsib.on.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.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

all inboxes | Powered by JetHome®