Date: Thu, 30 Mar 2000 12:44:00 -0700 From: Warner Losh <imp@village.org> To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> Cc: dcs@newsguy.com, freebsd-mobile@FreeBSD.org Subject: Re: Call for review: new pccard.conf scheme Message-ID: <200003301944.MAA26112@harmony.village.org> In-Reply-To: Your message of "Fri, 31 Mar 2000 04:19:17 %2B0900." <200003301919.EAA20801@tasogare.imasy.or.jp> References: <200003301919.EAA20801@tasogare.imasy.or.jp> <200003300407.VAA19618@harmony.village.org>
index | next in thread | previous in thread | raw e-mail
In message <200003301919.EAA20801@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : to plain FreeBSD, also to think "what kind of features are necessary : for the pccard daemon program in new pccard support". I'd like to hash out some ideas that I had in the card driving to work this morning. Right now the plan is for the pccard device drivers to know what kind of devices they grok. So the sio device would know all the modem cards it supports, in addition to being able to make its best shot at all serial devices (the CIS gives a function ID for each major function on a card). The ed driver would know what it supported, plus that if it was a network card to give it its best shot and probe the thing anyway (since 99% of all new network cards use ed or ep). And so forth. The ata driver will do similar things. This is just like NetBSD does it, except for the best effort probing of the card, which is what I'd like to add. I'm not completely sure about this part. I'm torn between having a new probe-like routine that will probe based on function and just having things silently do this. While this will take care of 99% of all users, there will be those users that need to be able to tell a driver "hey, mr Sn driver, please make a card that matches <XXXX> be matched by your probe routine." This will allow people to go out and buy the latest pccard and then let the driver know via a simple command that it should support attach to this card w/o the need to rebuild a driver. I was thinking of having a new command, called for the moment cardctl, that would do this. You'd say something like cardctl sio -o 0x0143 -m 0x1234 which would cause the sio driver to now match OEM number 0x143, model 0x1234. This would translate into a ioctl that would filter down to the pccard bus. The pccard bus would then issue a new bus method call to add the device id. The sio driver would get this call, make a note of it. After all returning, the pccard bus would (or the cardctl program would instruct tell the pccard bus to) do a probe_and_attach for all children not already attached. This would mean that we'd need to have some infrastructure to initialize a PnP id table for drivers to use, plus some infrastructure to add entries to an existing PnP table. All drivers would effectively have to support this, so maybe some factoring could be done to turn control of the table over to the pccard bus so that drivers don't need to get involved at all. Anyway, these are just my random musings at the moment. I'm sure people will let me know if I'm out to lunch or not. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003301944.MAA26112>