From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Hourihane Subject: Re: obtaining acpi details outside of drivers/acpi Date: Thu, 06 Sep 2007 14:57:24 +0100 Message-ID: <1189087044.7969.61.camel@localhost> References: <1189073769.7969.32.camel@localhost> <200709060743.42060.lenb@kernel.org> <1189079221.7969.40.camel@localhost> <200709060922.50337.lenb@kernel.org> <1189086833.7969.58.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from fairlite.demon.co.uk ([80.176.228.186]:38078 "EHLO fairlite.demon.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932088AbXIFN50 (ORCPT ); Thu, 6 Sep 2007 09:57:26 -0400 In-Reply-To: <1189086833.7969.58.camel@localhost> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Len Brown Cc: linux-acpi@vger.kernel.org On Thu, 2007-09-06 at 14:53 +0100, Alan Hourihane wrote: > On Thu, 2007-09-06 at 09:22 -0400, Len Brown wrote: > > On Thursday 06 September 2007 07:47, Alan Hourihane wrote: > > > > > Mmm. It seems acpi_video_bus_check() is static and therefore not > > > available outside of video.c > > > > > > > BTW. I'm curious what you are trying to do. > > > > There is actually quite a bit of movement in this code right now. > > > > > > Think about fbdev drivers (or some video driver).... Rather than > > > bang on the hardware to try and do auto-detection of devices, it's much > > > easier (and sometimes required) to just ask the system BIOS via ACPI to > > > see what devices are available. > > > > > > I want to parse _DOD myself to see what's available in kernel space. > > > > It would be good to have this code in only one place > > and export it from there to other parts of the kernel that need it. > > I'd like to be able to not have fbdev drivers depend on the acpi video driver, > > so perhaps we could have some generic interface where fbdev is the consumer > > and in this case acpi/video.c is the provider? > > That sounds good. I'm open to suggestions on interface. I'm willing to help define this though, so I don't expect anyone to just throw something over the wall. > But is there anything better available now to scan the namespace in > current released kernels for _DOD ? Oh, and if not, not to worry. I'll stick with the fixed namespace check for now, until we can define the interface above. Thanks Len! Alan.