Date: Tue, 19 May 2009 13:55:14 +0900 From: Weongyo Jeong <weongyo.jeong@gmail.com> To: Lucius Windschuh <lwindschuh@googlemail.com> Cc: Sam Leffler <sam@freebsd.org>, current@freebsd.org Subject: Re: HEADSUP: uath(4) has been committed. Message-ID: <20090519045514.GD42412@weongyo.cdnetworks.kr> In-Reply-To: <90a5caac0905171510v17441d4na51a059f72f7ecae@mail.gmail.com> References: <20090407022956.GA71377@weongyo.cdnetworks.kr> <90a5caac0905161502x3771072n22d58111a235de24@mail.gmail.com> <4A0F419A.2020700@freebsd.org> <90a5caac0905171218r6de3473le8edcac3dab7e2bb@mail.gmail.com> <4A106B49.4020809@freebsd.org> <90a5caac0905171510v17441d4na51a059f72f7ecae@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 18, 2009 at 12:10:27AM +0200, Lucius Windschuh wrote: > Thanks for the commits. > > But... I forgot one thing: kldunload if_uath ; kldload if_uath on a > firmware-loaded device leads to this output: > > uath0: timeout waiting for reply to cmd 0x1 (1) > uath0: could not initialize adapter > 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 > > Is this also a known problem? Perhaps yes but it's some complicate to describe how it could be fixed. Could you please file a PR for this issue? I'll try to look a HAL for uath(4) and find a method to solve it. regards, Weongyo Jeong
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090519045514.GD42412>