Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752045AbWIHC2G (ORCPT ); Thu, 7 Sep 2006 22:28:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752043AbWIHC2G (ORCPT ); Thu, 7 Sep 2006 22:28:06 -0400 Received: from ccerelrim02.cce.hp.com ([161.114.21.23]:56869 "EHLO ccerelrim02.cce.hp.com") by vger.kernel.org with ESMTP id S1752039AbWIHC2C (ORCPT ); Thu, 7 Sep 2006 22:28:02 -0400 Message-ID: <4132.24.9.204.52.1157682479.squirrel@mail.cce.hp.com> In-Reply-To: <1157677028.2782.64.camel@sli10-desk.sh.intel.com> References: <1157573069.5713.24.camel@keithlap> <1157594624.2782.45.camel@sli10-desk.sh.intel.com> <200609070925.50145.bjorn.helgaas@hp.com> <1157677028.2782.64.camel@sli10-desk.sh.intel.com> Date: Thu, 7 Sep 2006 20:27:59 -0600 (MDT) Subject: Re: one more ACPI Error (utglobal-0125): Unknown exception code:0xFFFFFFEA [Re: 2.6.18-rc4-mm3] From: "Bjorn Helgaas" To: "Shaohua Li" Cc: "Bjorn Helgaas" , kmannth@us.ibm.com, "Moore, Robert" , "Len Brown" , "Mattia Dongili" , "Andrew Morton" , "lkml" , "linux acpi" , "KAMEZAWA Hiroyuki" User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal X-PMX-Version: 5.1.2.240295, Antispam-Engine: 2.3.0.1, Antispam-Data: 2006.9.7.185944 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1210 Lines: 27 > On Thu, 2006-09-07 at 09:25 -0600, Bjorn Helgaas wrote: >> If we decide that "try HID first, then try CID" is the right thing, >> I think we should figure out how to make that work. Maybe that >> means extending the driver model somehow. > Don't think it's easy, especially no other bus needs it I guess. I agree it's probably not easy, but I think having the right semantics is more important than fitting cleanly into the driver model. But I know that without code, I'm just venting hot air, not contributing to a solution. How's the ACPI driver model integration going, anyway? I seem to recall some patches a while back, but I don't think they're in the tree yet. > Do we really need the memory hotplug device returns pnp0c01/pnp0c02? > What's the purpose? I don't know. But I think Keith already determined that a BIOS change is not likely. I hate to ask for BIOS changes like this because it feels like asking them to avoid broken things in Linux. - 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/