Date: Tue, 15 Dec 1998 00:46:31 +0900 (JST) From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) To: jkh@zippy.cdrom.com Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, kjc@csl.sony.co.jp, nathan@rtfm.net, current@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: PAO Integration? Message-ID: <199812141546.AAA25255@afs.ntc.mita.keio.ac.jp> In-Reply-To: Your message of "Sun, 13 Dec 1998 17:29:34 JST". <34776.913537774@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <34776.913537774@zippy.cdrom.com> jkh@zippy.cdrom.com writes: >> And we appreciate that, believe me. I think Mike may have been a >> little too harsh in his original message and I think that everyone in >> core, at least, does appreciate the language problem and the fact that >> you guys are often "out of the loop" on a lot of things going on >> around here. It would help greatly, of course, if Tatsumi-san would >> come back and take up the commit privs we gave him for the purpose of >> creating closer cooperation. Has anyone even seen Mr. Hosokawa >> lately? Is he still alive? :-) I'm alive, but I haven't recieved any current@freebsd.org mails these days. I heard about this thread in other mailing list and I searched my mailbox, but I found that no current@freebsd.org mails in it. I unsubscribed current once, and subscribed it again, but no mails have come from current@freebsd.org... Hmm... (I'm writing this mail via mail-netnews gateway) BTW, I think that PAO for 2.2.8 and 3.0 are provided for convenience of users and should be integrated in smart way. For example, I think that pcic_probe/attach, resource allocation code, multiple windows support, and some very dirty hacks in PAO should be totally rewritten before integration, but TI support, regex in pccard.conf, function ID in pccard.conf, noirq in pccard.conf, broken CIS hack, etc. should be integrated in -current. But I can't spend time for these works because I'm very busy today. I think PAO for 3.0 is better startline for these works than PAO for 2.2.1, 2.2.2, 2.2.5,.... I hope many people works on the smart integration of PAO and I think I can help them. *I personally* don't think that newconfig is needed for *PAO*, but I think that better device driver implementation is needed for *FreeBSD*. If many people think newconfig is better implementation and FreeBSD uses it, I think that the experiences in PAO experimental code should be rewritten in newconfig way, and if everyone says new-bus is the best, PAO should be rewritten in new-bus way. I don't think that all PAO code should be in -current, but I think we've got many pracical knowledge of PC-card system from PAO, and I believe that these experiences are useful for future FreeBSD. -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812141546.AAA25255>