Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Mar 2015 12:06:26 -0400
From:      Anthony Jenkins <Anthony.B.Jenkins@att.net>
To:        Warner Losh <imp@bsdimp.com>
Cc:        freebsd-acpi@freebsd.org, Ian Smith <smithi@nimnet.asn.au>
Subject:   Re: [PATCH] ACPI CMOS region support rev. 5
Message-ID:  <5509A282.6070207@att.net>
In-Reply-To: <56B494A3-2058-4B7B-8183-646A46753A53@bsdimp.com>
References:  <20150222180817.GD27984@strugglingcoder.info> <54EB8C21.2080600@att.net> <2401337.2oUs7iAbtB@ralph.baldwin.cx> <54EF3D5D.4010106@att.net> <20150227222203.P38620@sola.nimnet.asn.au> <20150228125857.D1277@besplex.bde.org> <54F14368.4020807@att.net> <20150302002647.W42658@sola.nimnet.asn.au> <54F5E53D.1090601@att.net> <20150306025800.U46361@sola.nimnet.asn.au> <54F9D7E6.4050807@att.net> <5504FF32.3020202@att.net> <20150317001401.X22641@sola.nimnet.asn.au> <5506F00A.3030708@att.net> <5506FBE3.1000009@att.net> <20150317041624.K22641@sola.nimnet.asn.au> <55073442.5060005@att.net> <20150317222704.K22641@sola.nimnet.asn.au> <550825DE.7030406@att.net> <56B494A3-2058-4B7B-8183-646A46753A53@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 03/18/2015 11:29 AM, Warner Losh wrote:
>> On Mar 17, 2015, at 7:02 AM, Anthony Jenkins <Anthony.B.Jenkins@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
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5509A282.6070207>