From owner-freebsd-current Fri Dec 8 12:33: 6 2000 From owner-freebsd-current@FreeBSD.ORG Fri Dec 8 12:33:04 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id D5ACD37B400 for ; Fri, 8 Dec 2000 12:33:03 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eB8KgKF01901; Fri, 8 Dec 2000 12:42:20 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012082042.eB8KgKF01901@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Takanori Watanabe Cc: acpi-jp@jp.freebsd.org, current@FreeBSD.org Subject: Re: cvs commit: src/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 In-reply-to: Your message of "Fri, 08 Dec 2000 23:57:39 +0900." <200012081457.XAA78320@shidahara1.planet.sci.kobe-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Dec 2000 12:42:20 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message