From owner-freebsd-mobile Tue Jul 13 15:21:26 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B875115148 for ; Tue, 13 Jul 1999 15:21:13 -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 QAA21591 for ; Tue, 13 Jul 1999 16:21:12 -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 QAA50120 for ; Tue, 13 Jul 1999 16:20:02 -0600 (MDT) Message-Id: <199907132220.QAA50120@harmony.village.org> To: mobile@freebsd.org Subject: pccard and -current Date: Tue, 13 Jul 1999 16:20:02 -0600 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to find out what, exactly, the status of pccard is on -current. Since I've had my head in some experimental code for a long time, I no longer have a good feel for these things. Since this experimental code is going to take a while, I'd like to try to address whatever issues are currently present in the code. I've spent the better part of 4 hours this afternoon getting a good tree together. I have a good kernel, but need to do a build world, I think. My guess is that old drivers are working, but new-bus drivers (fdc and sio) are not. Is that the case? Also, are there any objections to my placing more explicit error messages for failure modes in pccardd/pccard,pcic drivers? I have added some locally (which got me to the point of realizing I needed a make buildworld). pccardd's error reporting on plain old FreeBSD has always been too oracular ("yes" or "no" w/o explaination) for my tastes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message