Re: HEADSUP: uath(4) has been committed.

On Mon, May 18, 2009 at 11:49:05PM +0200, Hans Petter Selasky wrote:
> On Sunday 17 May 2009, Lucius Windschuh wrote:
> > 2009/4/7 Weongyo Jeong <weongyo.jeong_at_gmail.com>
> >
> 
> Here's one more device, which is currently not listed in if_uath.c:
> 
> ugen3.10: <WPN111 Atheros Communications Inc> at usbus3, cfg=0 md=HOST 
> spd=HIGH (480Mbps) pwr=ON
> 
>   bLength = 0x0012 
>   bDescriptorType = 0x0001 
>   bcdUSB = 0x0200 
>   bDeviceClass = 0x00ff 
>   bDeviceSubClass = 0x0000 
>   bDeviceProtocol = 0x0000 
>   bMaxPacketSize0 = 0x0040 
>   idVendor = 0x1385 
>   idProduct = 0x5f01 
>   bcdDevice = 0x0001 
>   iManufacturer = 0x0001  <Atheros Communications Inc>
>   iProduct = 0x0002  <WPN111>
>   iSerialNumber = 0x0003  <1.0>
>   bNumConfigurations = 0x0001 
> 
> Resulting dmesg after running uathload:
> 
> uath0: timeout waiting for reply to cmd 0x4 (4)
> uath0: could not read capability 2
> uath0: could not get device capabilities
> device_attach: uath0 attach returned 35
> uath0: timeout waiting for reply to cmd 0x1 (1)
> uath0: could not initialize adapter
> device_attach: uath0 attach returned 35
> 
> Can this be fixed?

Because I don't have WPN111 stick which failed to buy in my local store
I couldn't test it fully but one thing you can try is that adding some
delays for each usb commands could be helpful like a attached patch.

Could you please test with attached patch and show results?  I think you
can increase or decrease delay values or add delays at other places.

regards,
Weongyo Jeong