[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1157594624.2782.45.camel@sli10-desk.sh.intel.com>
Date: Thu, 07 Sep 2006 10:03:44 +0800
From: Shaohua Li <shaohua.li@...el.com>
To: kmannth@...ibm.com
Cc: "Moore, Robert" <robert.moore@...el.com>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Len Brown <lenb@...nel.org>,
Mattia Dongili <malattia@...ux.it>,
Andrew Morton <akpm@...l.org>,
lkml <linux-kernel@...r.kernel.org>,
linux acpi <linux-acpi@...r.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: RE: one more ACPI Error (utglobal-0125): Unknown exception
code:0xFFFFFFEA [Re: 2.6.18-rc4-mm3]
On Thu, 2006-09-07 at 04:04 +0800, keith mannthey wrote:
> On Wed, 2006-09-06 at 11:59 -0700, Moore, Robert wrote:
> > From one of the ACPI guys:
> >
> > > Get hid
> > > Look for driver
> > > If you find a match, load it
> > > If no match, get CID
> > > Look for driver
> > > If you find a match, load it
> > > If you did not find an hid or cid match, punt
>
> I think this is what my patch is doing.
>
> when looking for a driver: (acpi_bus_find_driver)
> I check against the HID
> return if found
> Then I check against the CID
> return if found
> else
> punt
>
> Any objections to pushing this into -mm and dropping the motherboard
> change?
I'd prefer not take this way. The ACPI driver model is already mess
enough, let's don't make it worse. We are converting the ACPI driver
model to Linux driver model, this will make the attempt difficult.
We can let the motherboard driver not bind to your device (say we didn't
register the motherboard driver, but just reserve the resource of the
deivce). Is it ok to you? (I remember Bjorn said he wants to reserve the
mem region of the device too).
Thanks,
Shaohua
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists