From owner-freebsd-mobile Mon Aug 20 1:15:11 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 05C9B37B403 for ; Mon, 20 Aug 2001 01:15:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f7K8F7q33432 for ; Mon, 20 Aug 2001 02:15:08 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f7K8F7W48853 for ; Mon, 20 Aug 2001 02:15:07 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108200815.f7K8F7W48853@harmony.village.org> To: mobile@freebsd.org Subject: Thinkpad fix + MFC of Ian's eject improvements. Date: Mon, 20 Aug 2001 02:15:07 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org OK. It turns out that you can't mess with the interrupt routing bits of register 0x92 for thinkpads and have them work. This, despite the fact that the PIR table says that the chip should be connected directly to the interrupts.... So this patch does two things. First, it doesn't set the INTRTIE bit, which should help some of the laptops that don't route things to the same interrupt. Second, it doesn't touch bits 1 and 2 of register 0x92 which direct how interrupts are routed. This didn't break my dell and made the thinkpad work again. Someone else reported this fix for their machine as well, but I don't know if it was a thinkpad or not. Please test them and let me know what you have to say. http://people.freebsd.org/~imp/pcic-44rc1.diff.1 Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message