From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 25 16:37:17 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 955051065679 for ; Sun, 25 Oct 2009 16:37:17 +0000 (UTC) (envelope-from marco.broeder@gmx.eu) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id DC0558FC1D for ; Sun, 25 Oct 2009 16:37:16 +0000 (UTC) Received: (qmail invoked by alias); 25 Oct 2009 16:10:35 -0000 Received: from port-92-195-123-16.dynamic.qsc.de (EHLO localhost) [92.195.123.16] by mail.gmx.net (mp019) with SMTP; 25 Oct 2009 17:10:35 +0100 X-Authenticated: #23197544 X-Provags-ID: V01U2FsdGVkX18Wh+8h1qoWtyZnSbXhhnuO+jSsS1a4OAfYoY75bY qQD+JcnL9fpMsG From: Marco =?utf-8?q?Br=C3=B6der?= To: freebsd-stable@freebsd.org Date: Sun, 25 Oct 2009 17:09:49 +0100 User-Agent: KMail (FreeBSD) References: <4AE3A001.8000205@FreeBSD.org> In-Reply-To: <4AE3A001.8000205@FreeBSD.org> MIME-Version: 1.0 Message-Id: <200910251709.49850.marco.broeder@gmx.eu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Y-GMX-Trusted: 0 X-FuHaFi: 0.66 X-Mailman-Approved-At: Sun, 25 Oct 2009 17:29:38 +0000 Cc: Alexander Motin , FreeBSD-Current , icegloom dem , freebsd-amd64@freebsd.org Subject: Re: MCP55 SATA solution to test X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: marco.broeder@gmx.eu List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Oct 2009 16:37:17 -0000 On Sun October 25 2009 02:46:57 Alexander Motin wrote: > Hi. >=20 > Thanks to one man who provided access to his machine, I seem to found > how to fix device detection on nVidia MCP55 SATA controller on amd64 > 8.0. Looks like this controller need some time (very short) to enable > BAR(5) memory access after PCI configuration register written. Probably > some changes in PCI code exposed this issue. Also it explains why > setting hw.pci.mcfg to 0 helps. >=20 > Attached patch solves problem for that machine. Testers are welcome. >=20 Success! I tested your patch and everything is working fine with hw.pci.mcfg set to 1, now. Please commit it. Many thanks! =2D-=20 Regards, Marco Br=C3=B6der OpenPGP key fingerprint: 5615 106E 031A F3D3 64CC 0F9E 4DCE 6524 F595 082F