From owner-freebsd-mobile Fri Mar 16 13:52:38 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F31937B71A for ; Fri, 16 Mar 2001 13:52:35 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2GLqX937500 for ; Fri, 16 Mar 2001 14:52:34 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103162152.f2GLqX937500@harmony.village.org> To: mobile@freebsd.org Subject: Simple patches for IRQ enforcement Date: Fri, 16 Mar 2001 14:52:33 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please look at http://people.freebsd.org/~imp/Ppccard-irq for a patch that might help things. It requires that the irq for management be in the list of allowed ones (3, 4, 5, 7, 9, 10, 11, 12, 14, 15). In addition, it cleans up a few manifest constants that are in the driver now that I have the PD6710/'22 datasheet. It is amazing the number of things that you learn about hardware when you have a good datasheet for it. It also explicitly turns on the the "report management interrupts" flag in the PCIC_INT_GEN register. This is programmed on by most bioses, but some seem to not do it so we don't get management interrupts on those machines. This is especially true of a suspend/resume sequence. It also adds the 82365 to the list of chips we do special things for for power. While the original 82365 didn't support 3.3V operations, many clones do. And they do it in the PD67xx way, it would appear. Since these registers are not used on the 82365, this should be OK as the 3.3V stuff will fail later anyway. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message