From owner-freebsd-hackers Wed Dec 15 16:25:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5D95515632 for ; Wed, 15 Dec 1999 16:25:24 -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 RAA79080; Wed, 15 Dec 1999 17:25:19 -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 RAA65931; Wed, 15 Dec 1999 17:25:19 -0700 (MST) Message-Id: <199912160025.RAA65931@harmony.village.org> To: Michael Kennett Subject: Re: pccard disruptions : how did it go? Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 16 Dec 1999 07:52:54 +0800." <199912152352.HAA09649@laurasia.com.au> References: <199912152352.HAA09649@laurasia.com.au> Date: Wed, 15 Dec 1999 17:25:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912152352.HAA09649@laurasia.com.au> Michael Kennett writes: : To confirm: : : The new pccard code contains the `controller pccard' config directive. : - the source code is in sys/dev/pcic : sys/dev/pccard : : The old pccard code contains the `controller card' config directive. : - the source code is in sys/pccard : : Is this correct ? Yes. That's right. : Thank you for your help. I'm not asking you to do it all, but : instead what needs to be done, and in what direction I should be : going! I think hacking the xe driver to work with the newbus kludge : is less than desirable. Instead, I'd like to aim for support under : the new pccard code. It is indended attach will be the same, and that probe will nearly be the same, at least at first. The probe code for the drivers will be longer for newcard in that it will have to claim the device if the driver supports it. In the old pccard code probe is just a nice dummy which calls the usual probe routine for its side effects (the sio driver's probe routine leaves the uart in a known state, for example). I've been toying with the idea of having an identify routine which would make it possible to have the same binary for both the old driver and new, but that's not completely settled. I'm slogging through hooking up the newbus routines to the old chip tag stuff. I need to map the rid into the window that they currently return. I also need to figure out how to get the card's address (in card space) mapped with the allocation routines that we have now. Then I move into pccard and convert the chip tag calls into newbus calls. I also need to go through and make sure that the softc/ivars stuff connected and working properly. The pcic is the bridge driver. It will have n children, one per slot. Each slot will have zero or more children drivers based on the cards that are connected. It is intended that we'll support multiple functions in this way. The pccard children devices will have pcic_ivars as their ivars. The children of the pccard children will have pccard_ivars. : However, I've noticed that the file /dev/pcic/i82365_isasubr.c is missing : from the Dec 12 -current sources, and compilation fails for `controller : pccard'. Did you rerun config (or did I botch the commit and not commit conf/files wich removed it)? Oh, looks like my botch.... sorry about that... fixed. What can you do to help? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message