From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 16:57:27 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 8EE8A1065672; Wed, 8 Apr 2009 16:57:27 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Wed, 8 Apr 2009 12:56:37 -0400 User-Agent: KMail/1.6.2 References: <1239063789.00097213.1239052203@10.7.7.3> <200904071757.04734.jkim@FreeBSD.org> <83e5fb980904080424w1dda7fb3tf1c26ac72752352f@mail.gmail.com> In-Reply-To: <83e5fb980904080424w1dda7fb3tf1c26ac72752352f@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200904081257.18260.jkim@FreeBSD.org> Cc: Alexander Motin , Diego Depaoli Subject: Re: AMD 780G chipset major issues 1/3 (ata, ataati) 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, 08 Apr 2009 16:57:28 -0000 On Wednesday 08 April 2009 07:24 am, Diego Depaoli wrote: > On Tue, Apr 7, 2009 at 11:57 PM, Jung-uk Kim wrote: > > I have a similar board and it seems to share the broken ACPI > > DSDT. > > At this point I consider acpi's issues very minor issues. > The hard reality is than I can't install and run FreeBSD out of the > box on such board bought in the last five years (and I do not ever > buy products just released on the market). These days ACPI does a lot more than you may think. ;-) Actually, the BIOS writer *tried* to configure SATA controller modes differently depending on BIOS options you have selected when DSDT is loaded but that is one of the things ignored if my assumption was correct, i.e., sharing broken DSDT. Try dumping DSDT and see it for yourself. You may see something like this: Device (SATA) { Name (_ADR, 0x00110000) If (LEqual (STCL, 0x0101)) <--- "executable at module level" { ... <--- This entire block is ignored! } } Within the block, it sets PCI BARs and stuff for atapci0 and enables its channels via _STA methods. Without the south bridge documentation[1], we cannot do anything to mimic what it does from ataati(4). Jung-uk Kim [1] The situation may change in the future, though: http://forums.amd.com/devforum/messageview.cfm?catid=203&threadid=110538