Date: Wed, 2 Nov 2005 16:29:58 +1100
From: Andrew Morton <akpm@osdl.org>
To: matthieu castet <castet.matthieu@free.fr>
Cc: 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
Message-Id: <20051102162958.11c1983a.akpm@osdl.org>
In-Reply-To: <43677257.4090506@free.fr>
References: <4363F9B5.6010907@free.fr>
	<20051031155803.2e94069f.akpm@osdl.org>
	<200511011340.41266.duncan.sands@math.u-psud.fr>
	<43677257.4090506@free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1375
Lines: 34

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)?

Because other drivers may hit this problem (whatever it is) and fixes in
core kernel might be needed.  If we just work around stuff, core kernel
remains unfixed...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/