From owner-freebsd-current Tue May 4 0:47: 6 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 943DB15274 for ; Tue, 4 May 1999 00:47:04 -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.9.3/8.9.3) with ESMTP id BAA08807; Tue, 4 May 1999 01:46:22 -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.9.3/8.8.3) with ESMTP id BAA55988; Tue, 4 May 1999 01:47:41 -0600 (MDT) Message-Id: <199905040747.BAA55988@harmony.village.org> To: Doug Rabson Subject: Re: Odd message during -current boot Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 04 May 1999 08:41:35 BST." References: Date: Tue, 04 May 1999 01:47:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug Rabson writes: : In that case, the driver will detect it when it allocates the resource. It : will after conversion anyway :-). :-) : > The other one which is needed reconfig_isadev, which is used by the zp : > and ze drivers. It is only called after a resume and its lack is what : > causes these devices to not work after a resume. : : Nasty. Is it worth trying to fix this or will you be changing the zp : driver anyway with the pccard work? No. Come to think of it the zp and ze drivers should die when ep and whatever ed (or whatever ze replaces) are converted to the new new scheme. That may be a while yet, since I'm still working on the new old scheme. The new new scheme lacks pccardd for anything but dynamic command running after a device has been added to the system, and maybe some configuration stuff. The pccards will probe on insertion, and attach w/o the need for pccardd. This should help the many configuration problems people have had with pccard. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message