Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758921Ab0FBXpc (ORCPT ); Wed, 2 Jun 2010 19:45:32 -0400 Received: from mail-yw0-f179.google.com ([209.85.211.179]:42788 "EHLO mail-yw0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758812Ab0FBXpb (ORCPT ); Wed, 2 Jun 2010 19:45:31 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ZuRdAONOtfHVgiCghTlueIz9KzDscoUtOQMZxCvwxkISIjz1VE05u5nMSv3ncp0aDy nlmWAMRktIUe3QyAC/1gkk25o+BLYqDLbsrvWidnR4TxbCOkQWOzekIS5xwIzOpdD8yB /fKsrCmnO18zwfoLuH1GOLq5C8iceCSrh00vw= Message-ID: <4C06ED18.2010400@gmail.com> Date: Wed, 02 Jun 2010 17:45:28 -0600 From: Robert Hancock User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4 MIME-Version: 1.0 To: "Justin P. Mattock" CC: Matthew Garrett , x86@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table. References: <20100601192101.GA15086@srcf.ucam.org> <4C056839.8020605@gmail.com> <20100601200704.GA16091@srcf.ucam.org> <4C056AE6.3000409@gmail.com> <20100601202130.GA16391@srcf.ucam.org> <4C056E0C.2030709@gmail.com> <20100601203351.GA16575@srcf.ucam.org> <4C0572B4.6000201@gmail.com> <20100601211219.GA17719@srcf.ucam.org> <4C057AE9.9020307@gmail.com> <20100601212901.GA18390@srcf.ucam.org> <4C057EF0.2030808@gmail.com> <4C05E800.1010400@gmail.com> <4C05F3BF.6090503@gmail.com> <4C06ECAA.3060708@gmail.com> In-Reply-To: <4C06ECAA.3060708@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3013 Lines: 107 On 06/02/2010 05:43 PM, Justin P. Mattock wrote: > On 06/02/2010 04:18 PM, Robert Hancock wrote: >> On Wed, Jun 2, 2010 at 12:01 AM, Justin P. Mattock >> wrote: >>>> Can you post the FACP section of the acpidump output from this machine? >>>> >>> >>> here you go: >>> >> >> >>> Reset Register Supported (V2) : 1 >> >>> [074h 116 12] Reset Register : >>> [074h 116 1] Space ID : 01 (SystemIO) >>> [075h 117 1] Bit Width : 08 >>> [076h 118 1] Bit Offset : 00 >>> [077h 119 1] Access Width : 00 >>> [078h 120 8] Address : 0000000000000CF9 >>> >>> [080h 128 1] Value to cause reset : 06 >> >> Hmm, so the FADT says the reset register is listed as supported, and >> says writing 0x06 to 0xCF9 is supposed to do it.. That's exactly what >> this should do: >> >> #include >> >> int main() { >> iopl(3); >> outb(6, 0xcf9); >> return 0; >> } >> >> but you said that didn't do anything.. It kind of seems like ACPI >> reboot is busted on this machine then, but then I wonder how Windows >> manages to work.. >> > > > alright!! I have a better idea at what this is now.. > as for the above code, yes this one segfaults, > the other code posted on the thread just returns > a command prompt(testing: You get a segfault on that one? Running as root? > > #include > > int main() { > iopl(3); > outb(0xfe, 0xcf9); > return 0; > } > on a dell reboot's as is.) > > both my macbook, and imac are > broken with the above.(but for whatever > reason the macbook doesnt need an dmi entry > in reboot.c just iMac9,1 etc..) > > so the address for the CF9 is this: > > [074h 116 12] Reset Register : > [074h 116 1] Space ID : 01 (SystemIO) > [075h 117 1] Bit Width : 08 > [076h 118 1] Bit Offset : 00 > [077h 119 1] Access Width : 00 > [078h 120 8] Address : 0000000000000CF9 > > [080h 128 1] Value to cause reset : 06 > [081h 129 3] Reserved : 000000 > [084h 132 8] FACS Address : 00000000BFECD000 > [08Ch 140 8] DSDT Address : 00000000BFEE0000 > [094h 148 12] PM1A Event Block : > [094h 148 1] Space ID : 01 (SystemIO) > [095h 149 1] Bit Width : 20 > [096h 150 1] Bit Offset : 00 > [097h 151 1] Access Width : 00 > [098h 152 8] Address : 0000000000000400 > > not sure how to read this, but are there > two devices here i.g. > is the top a cold boot(reset register) and > the bottom(value to cause reset) a warm boot? No, the stuff after "Value to cause reset" is something else entirely. > > at the moment I'm trying to figure out what/where > *((unsigned short *)__va(0x472)) = reboot_mode; > 0x472 comes from as well as 0x1234 then > #define KBD_STATUS_REG 0x64 > to see if I can see anything. > > > thanks for the info on this.. > > Justin P. Mattock > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/