From owner-freebsd-current Tue Jul 10 19:18:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (cust-P5-R11-246.POOL.ESR.SJO.wwc.com [206.112.122.246]) by hub.freebsd.org (Postfix) with ESMTP id 4419937B40B for ; Tue, 10 Jul 2001 19:18:52 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6B2Wm102658; Tue, 10 Jul 2001 19:32:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107110232.f6B2Wm102658@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Munehiro Matsuda Cc: acpi-jp@jp.freebsd.org, current@freebsd.org, yoichi@eken.phys.nagoya-u.ac.jp Subject: Re: [acpi-jp 1165] Re: HEADS UP - more ACPI updates, CPU throttling In-reply-to: Your message of "Tue, 10 Jul 2001 22:33:51 +0900." <20010710223351H.haro@h4.dion.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Jul 2001 19:32:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I'm also having same hang-up, with acpi_pcib.c rev1.10 (no NEWCARD). Sounds like calling _SRS is breaking something. > With acpi_pcib.c rev1.9, I loose my pccard. This is known; I messed it up. 8( > With acpi_pcib.c rev1.8, everything seems ok. This uses the "old" PCI interrupt routing code. -- ... 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