From owner-freebsd-current@FreeBSD.ORG Wed Dec 10 10:44:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4A2A106564A for ; Wed, 10 Dec 2008 10:44:33 +0000 (UTC) (envelope-from sos@freebsd.org) Received: from deepcore.dk (adsl.deepcore.dk [87.63.29.106]) by mx1.freebsd.org (Postfix) with ESMTP id 6F6DB8FC16 for ; Wed, 10 Dec 2008 10:44:33 +0000 (UTC) (envelope-from sos@freebsd.org) Received: from [172.18.2.117] (axiell-gw1.novi.dk [77.243.61.137]) by deepcore.dk (8.14.3/8.14.2) with ESMTP id mBAAI5Hn029871; Wed, 10 Dec 2008 11:18:05 +0100 (CET) (envelope-from sos@freebsd.org) Message-Id: <237FB18B-DACD-45F9-85DF-E214A33FDE5F@freebsd.org> From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= To: "Conrad J. Sabatier" In-Reply-To: <20081206190754.6c2bbd70@serene.no-ip.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 10 Dec 2008 11:18:05 +0100 References: <20081128234155.0221e263@serene.no-ip.org> <4930D7CE.4080909@psg.com> <20081202220643.72eb52a3@serene.no-ip.org> <20081203151537.GA1045@phenom.cordula.ws> <20081206190754.6c2bbd70@serene.no-ip.org> X-Mailer: Apple Mail (2.929.2) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (deepcore.dk [87.63.29.106]); Wed, 10 Dec 2008 11:18:06 +0100 (CET) Cc: freebsd-current@freebsd.org, cpghost Subject: Re: i give up 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: Wed, 10 Dec 2008 10:44:34 -0000 On 7Dec, 2008, at 2:07 , Conrad J. Sabatier wrote: > > As another poster suggested, it's possible there's a bug/typo in the > patches Soren sent me, although they all apply quite cleanly to every > successive version of current I've tried them on. So...I'm at a loss > at this point. It really is frustrating. > In fact it seems there is a typo in that patch, you need to use the =20 ATA_NFORCE_MCP77_A8 device ID instead of the ATA_NFORCE_MCP77_A1 in =20 the patch to match your HW. However, you should have been able to tell that pretty quickly by =20 looking at the ID's you sent back when and the patch ;) Anyhow there is just that much I can do in situations like this, I =20 only have limitted time and cannot possibly attend to all the problems =20= I get in my inbox in a timely manner, sorry. "life sucks - and then you die" -S=F8ren