> On Mar 18, 2015, at 9:59 AM, Anthony Jenkins
> wrote:
>
> On 03/18/2015 11:26 AM, Warner Losh wrote:
>> Looking at patch 5:
>>
>> You need to rework this so there’s an atrtc_acpi.c. Put all the ACPI
>> attachment in there.
>
> Okay, shouldn't be a problem.
>
>> You should also split off t
> On Mar 18, 2015, at 10:06 AM, Anthony Jenkins
> wrote:
>
> On 03/18/2015 11:29 AM, Warner Losh wrote:
>>> On Mar 17, 2015, at 7:02 AM, Anthony Jenkins
>>> wrote:
\Where else might ATRTC_VERBOSE be set otherwise?
>>> I'm picturing a (future?) config(5) knob, e.g.
>>>
>>> device atrtc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/17/2015 08:28, Ian Smith wrote:
> 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.
For runtime, p
On 03/18/2015 11:29 AM, Warner Losh wrote:
>> On Mar 17, 2015, at 7:02 AM, Anthony Jenkins
>> 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 tim
On 03/18/2015 11:26 AM, Warner Losh wrote:
> Looking at patch 5:
>
> You need to rework this so there’s an atrtc_acpi.c. Put all the ACPI
> attachment in there.
Okay, shouldn't be a problem.
> You should also split off the little bit that’s ISA-specific into atrtc_isa.
You mean rtcin() and writ
> On Mar 17, 2015, at 7:02 AM, Anthony Jenkins
> 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 sho
Looking at patch 5:
You need to rework this so there’s an atrtc_acpi.c. Put all the ACPI attachment
in there. You should also split off the little bit that’s ISA-specific into
atrtc_isa. Once you do that, we can talk.
Warner
signature.asc
Description: Message signed with OpenPGP using GPGMai
