From: Alan Hourihane <alanh@fairlite.demon.co.uk>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: obtaining acpi details outside of drivers/acpi
Date: Thu, 06 Sep 2007 12:47:01 +0100 [thread overview]
Message-ID: <1189079221.7969.40.camel@localhost> (raw)
In-Reply-To: <200709060743.42060.lenb@kernel.org>
On Thu, 2007-09-06 at 07:43 -0400, Len Brown wrote:
> Hi Alan,
>
> Yes, pathnames are arbitrary, don't use them.
>
> Look in drivers/acpi/video.c for acpi_video_bus_check()
> As the video device has no HID, this routine is basically
> used to check all the drivers in the tree if they have _DOD
> and the other stuff a video device should have.
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.
What else can I use ?
Alan.
next prev parent reply other threads:[~2007-09-06 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 10:16 obtaining acpi details outside of drivers/acpi Alan Hourihane
2007-09-06 11:43 ` Len Brown
2007-09-06 11:47 ` Alan Hourihane [this message]
2007-09-06 13:22 ` Len Brown
2007-09-06 13:27 ` Alexey Starikovskiy
2007-09-06 13:53 ` Alan Hourihane
2007-09-06 13:57 ` Alan Hourihane
2007-09-06 14:17 ` Alexey Starikovskiy
2007-09-06 14:33 ` Alan Hourihane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1189079221.7969.40.camel@localhost \
--to=alanh@fairlite.demon.co.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.