From owner-freebsd-current@FreeBSD.ORG Thu Jan 3 09:47:31 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 A73D116A418 for ; Thu, 3 Jan 2008 09:47:31 +0000 (UTC) (envelope-from bofh@terranova.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id 80BCC13C455 for ; Thu, 3 Jan 2008 09:47:31 +0000 (UTC) (envelope-from bofh@terranova.net) Received: from [216.89.228.170] (host-216-89-228-170.wireless.terranova.net [216.89.228.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tog.net (Postfix) with ESMTP id A563129B5FB for ; Thu, 3 Jan 2008 04:47:30 -0500 (EST) Message-ID: <477CAF30.7020703@terranova.net> Date: Thu, 03 Jan 2008 04:47:28 -0500 From: Travis Mikalson Organization: TerraNovaNet Internet Services User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1497D115-2534-4799-9D8E-18A267DF0B62@mipster.net> <9A374150-DC2A-439D-A205-E8867B663C5A@mipster.net> <477B0B07.8080703@terranova.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: ServerWorks/Broadcom HT1000 chipset errata saga 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: Thu, 03 Jan 2008 09:47:31 -0000 Nick Pope wrote: > I csup'ed to latest RELENG_7_0 (RC1) and built the GENERIC kernel. I'm > assuming Soren's patch has made it into RC1 because, without commenting > out the rr232x driver, the kernel mis-detects my Supermicro PCI-X SATA > controller (MV88SX6081 chipset) as an rr232x. No, Søren's HT1000/Marvell fixing stuff is still in HEAD only according to cvsweb. Did not make it to RELENG_7 or RELENG_7_0 yet. I think your problem is unrelated to this patchset. It wasn't making any sense that any of this code that was touched would have any effect on detection of your Marvell device anyway...