public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: matthieu castet <castet.matthieu@free.fr>,
	duncan.sands@math.u-psud.fr,
	linux-usb-devel@lists.sourceforge.net,
	usbatm@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]  Eagle and ADI 930 usb adsl modem driver
Date: Wed, 2 Nov 2005 14:27:14 -0800	[thread overview]
Message-ID: <20051102222714.GA23543@kroah.com> (raw)
In-Reply-To: <20051102162958.11c1983a.akpm@osdl.org>

On Wed, Nov 02, 2005 at 04:29:58PM +1100, Andrew Morton wrote:
> matthieu castet <castet.matthieu@free.fr> wrote:
> >
> > Hi Duncan,
> > 
> > Duncan Sands wrote:
> > > Hi Andrew,
> > > 
> > > 
> > > this code looks like a 'orrible hack to work around a common problem
> > > with USB modem's of this type: if the modem is plugged in while the
> > > system boots, the driver may look for firmware before the filesystem
> > 
> > No, it wasn't the problem, even when loading with insmod/modprobe the 
> > timeout occurs on some configurations. For example on 
> > http://atm.eagle-usb.org/wakka.php?wiki=TestUEagleAtmBaud123, you could 
> > see the 'firmware ueagle-atm/eagleIII.fw is not available' error.
> > 
> > It is only happen for pre-firmware modem (uea_load_firmware) ie where we 
> > just do a request_firmware in the probe without any initialisation before.
> > So the problem seems to appear when we do a request_firmware too early 
> > in the usb_probe.
> > 
> 
> Can you please work out exactly what's happening and come up with a more
> solid solution than msleep(1)?

The fix is to use the async firmware interface, no sleeping or timeouts
needed.

thanks,

greg k-h

  reply	other threads:[~2005-11-02 23:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 22:37 [PATCH] Eagle and ADI 930 usb adsl modem driver matthieu castet
2005-10-31 23:58 ` Andrew Morton
2005-11-01 12:40   ` Duncan Sands
2005-11-01 13:04     ` David Woodhouse
2005-11-01 13:12       ` Marco d'Itri
2005-11-02  7:42       ` Duncan Sands
2005-11-02  7:45         ` David Woodhouse
2005-11-02  8:02           ` Duncan Sands
2005-11-02 10:46       ` Roman Kagan
2005-11-02 11:01         ` Duncan Sands
2005-11-01 13:49     ` matthieu castet
2005-11-02  5:29       ` Andrew Morton
2005-11-02 22:27         ` Greg KH [this message]
2005-11-02  7:45       ` Duncan Sands
2005-11-01 14:08   ` matthieu castet
2005-11-02  5:34     ` Andrew Morton
2005-11-02  7:47     ` Duncan Sands
2005-11-01 22:45 ` Greg KH
2005-11-02  7:54   ` Duncan Sands
2005-11-02  8:03     ` Greg KH
2005-11-02  8:45       ` [linux-usb-devel] " Oliver Neukum
2005-11-02  8:52         ` Duncan Sands
2005-11-02 21:39           ` Greg KH
2005-11-02 21:37         ` Greg KH
2005-11-02 15:56   ` Alan Stern
2005-11-02 20:15   ` matthieu castet
2005-11-02 21:18     ` matthieu castet
2005-11-07 17:47       ` Greg KH
2005-11-06 18:44     ` matthieu castet
2005-11-07 17:47       ` Greg KH
2005-11-07 17:46     ` Greg KH
2005-11-07 18:47       ` matthieu castet
2005-11-07 22:27       ` matthieu castet
2005-11-07 23:02         ` matthieu castet

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=20051102222714.GA23543@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=castet.matthieu@free.fr \
    --cc=duncan.sands@math.u-psud.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=usbatm@lists.infradead.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