Date: Mon, 18 May 2009 23:49:05 +0200 From: Hans Petter Selasky <hselasky@freebsd.org> To: freebsd-current@freebsd.org Cc: Lucius Windschuh <lwindschuh@googlemail.com>, Weongyo Jeong <weongyo@freebsd.org> Subject: Re: HEADSUP: uath(4) has been committed. Message-ID: <200905182349.06150.hselasky@freebsd.org> In-Reply-To: <90a5caac0905161502x3771072n22d58111a235de24@mail.gmail.com> References: <20090407022956.GA71377@weongyo.cdnetworks.kr> <90a5caac0905161502x3771072n22d58111a235de24@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 17 May 2009, Lucius Windschuh wrote: > 2009/4/7 Weongyo Jeong <weongyo.jeong@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? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905182349.06150.hselasky>