From owner-freebsd-current Tue Nov 30 7:27:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A43A015917 for ; Tue, 30 Nov 1999 07:27:15 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA08898; Tue, 30 Nov 1999 08:27:14 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA02427; Tue, 30 Nov 1999 08:27:49 -0700 (MST) Message-Id: <199911301527.IAA02427@harmony.village.org> To: Nick Hibma Cc: FreeBSD CURRENT Mailing List In-reply-to: Your message of "Tue, 30 Nov 1999 13:02:08 +0100." References: Date: Tue, 30 Nov 1999 08:27:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : pcic: polling, can't alloc 0 : pcic: polling, can't alloc 0 This isn't your problem, but you might want to assign an interrupt line to these devices. Another problem is that I didn't implement the logic in the right way for the nbk. In many places I treat things as having one pccard device, when there is one per child. The pcic should tell the pccard child that an eject/socket power off has occurred and the pccard child should then detach all its children at that point. I was in a hurry and didn't do this like I should have. That might be an easier road to a fix as well. I'm *STILL* waiting for the returned laptop to come back. Grump. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message