From: Alexey Starikovskiy <aystarik@gmail.com>
To: Len Brown <lenb@kernel.org>
Cc: Alan Hourihane <alanh@fairlite.demon.co.uk>, linux-acpi@vger.kernel.org
Subject: Re: obtaining acpi details outside of drivers/acpi
Date: Thu, 06 Sep 2007 17:27:04 +0400 [thread overview]
Message-ID: <46E00028.1050205@gmail.com> (raw)
In-Reply-To: <200709060922.50337.lenb@kernel.org>
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?
There is module autoloading code in acpi/scan.c which might be helpful.
Just look for acpi_video_bus_match().
Regards,
Alex.
>
> -Len
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-09-06 13:27 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
2007-09-06 13:22 ` Len Brown
2007-09-06 13:27 ` Alexey Starikovskiy [this message]
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=46E00028.1050205@gmail.com \
--to=aystarik@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).