> >  Modified files:
> >    sys/dev/acpica       acpi.c acpi_button.c acpi_ec.c acpi_isa.c 
> >                         acpi_lid.c acpi_pcib.c acpi_processor.c 
> >                         acpi_resource.c acpi_thermal.c 
> >                         acpi_timer.c acpiio.h acpivar.h 
> >  Log:
> >   - Convert a lot of homebrew debugging output to use the ACPI CA debugging
> >     infrastructure.  It's not perfect, but it's a lot better than what
> >     we've been using so far.  The following rules apply to this:
> >      o BSD component names should be capitalised
> >      o Layer names should be taken from the non-CA set for now.  We
> >        may elect to add some new BSD-specific layers later.
> I don't think this "infrastructure" is useful. As far as I experienced,
> the message is too noisy or too few infomation.

I've been very slowly coming around to like it.  It's important to pick 
your debugging options carefully, and to be prepared to wade through 
thousands of lines of output (a serial console is mandatory).

However, I've been careful to keep the BSD parts separate from the ACPI 
CA parts, so you can just turn on the BSD-related debugging without 
getting the eleven bazillion mutex operations, etc logged.

I also added the ! support *specifically* so that I can turn lots of 
stuff on, and then turn the really noisy and useless stuff off again.

But most importantly, I didn't have anything better up my sleeve.  If 
you've got a better integrated debugging infrastructure, I'm all ears. 8)

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to