From owner-freebsd-current@FreeBSD.ORG Sun May 21 20:54:40 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 002D116A6EB for ; Sun, 21 May 2006 20:54:39 +0000 (UTC) (envelope-from current@dino.sk) Received: from mail.netlab.sk (mail.netlab.sk [213.215.72.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F24043D48 for ; Sun, 21 May 2006 20:54:36 +0000 (GMT) (envelope-from current@dino.sk) Received: from [192.168.16.13] (home.dino.sk [213.215.74.194]) (AUTH: PLAIN milan@netlab.sk, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.netlab.sk with esmtp; Sun, 21 May 2006 23:00:29 +0200 id 00289C12.4470D4ED.0000268D From: Milan Obuch To: freebsd-current@freebsd.org Date: Sun, 21 May 2006 22:54:14 +0200 User-Agent: KMail/1.9.1 References: <200605160920.33323.current@dino.sk> <20060516085912.GA88689@walton.maths.tcd.ie> <200605170959.33082.current@dino.sk> In-Reply-To: <200605170959.33082.current@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605212254.15332.current@dino.sk> Subject: Re: Weird thing - pciconf reading differs in two systems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2006 20:54:42 -0000 On Wednesday 17 May 2006 09:59, Milan Obuch wrote: > On Tuesday 16 May 2006 10:59, David Malone wrote: > > On Tue, May 16, 2006 at 09:20:32AM +0200, Milan Obuch wrote: > > > This makes me wonder - how could the same card be identified as two > > > different devices? I tested the same card, then another one and the > > > result is the same. Working in my tablet, not working in WRAP. There is > > > one difference, however - kernel in WRAP has ath built-in, in my tablet > > > I am kldloading it. > > > > Could be loose connections in the WRAP - if some of the pins are not > > connected properly that could result in 0xff showing up in various > > places (or worse). > > > > David. > > I do not think it's the case. I did test it with two boards, in three > slots. Were it loose connector, it would not be for any combination of > card/slot on WRAP, but not else. I will try it once more, on some other > machine/other boards and we'll see the result. > > Milan After some testing, I found there is issue with reset timing in v1.09 and v1.10 WRAP's bios versions. Version v1.11 seems to be working. Just if someone sees similar issue, BIOS update could be the solution. Milan -- No need to mail me directly. Just reply to mailing list, please.