[PATCH] ACPI CMOS region support rev. 5

Anthony Jenkins Anthony.B.Jenkins at att.net
Wed Mar 18 16:06:34 UTC 2015


On 03/18/2015 11:29 AM, Warner Losh wrote:
>> On Mar 17, 2015, at 7:02 AM, Anthony Jenkins <Anthony.B.Jenkins at att.net> wrote:
>>> \Where else might ATRTC_VERBOSE be set otherwise?
>> I'm picturing a (future?) config(5) knob, e.g.
>>
>>    device atrtc
>>    options ATRTC_VERBOSE=1
>>
>>
>> so it can be set at compile time.
> Why not just boot verbose? history has shown too many options like
> this is hard to use.

I think I understand what you're saying... I also prefer fewer config(5)
knobs.  So you're suggesting I determine (at runtime) the boot verbose
setting (kenv(2) or however it's properly done) and dump the
compile-time verbosity setting?

Thanks,
Anthony

>>> I still wonder if there isn't a global acpi_loaded_and_running variable
>>> so you could avoid even attempting ACPI init calls, perhaps making this
>>> not so dependent on ACPI, at least at runtime.
>> I haven't (yet) been able to find a compile-time flag that tells me if
>> the kernel supports ACPI; I'm /pretty/ sure the ACPI headers I'm
>> #include'ing will exist for every build of FreeBSD.
> I wouldn’t count on it. However, they may exist for all platforms that
> use atrtc.
>
> But it wouldn’t be an issue if you did a separate attachment.
>
> Warner
>



More information about the freebsd-acpi mailing list