From owner-freebsd-current Sat Dec 12 18:30:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29026 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:30:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (ykh28DS09.kng.mesh.ad.jp [133.205.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29021 for ; Sat, 12 Dec 1998 18:30:04 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA08579; Sun, 13 Dec 1998 02:40:58 +0900 (JST) Message-Id: <199812121740.CAA08579@chandra.eatell.msr.prug.or.jp> To: mike@smith.net.au, current@FreeBSD.ORG cc: MIHIRA Sanpei Yoshiro Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 16:06:54 JST." <199812120706.QAA22991@lavender.sanpei.org> Date: Sun, 13 Dec 1998 02:40:58 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PAO's assign_io function in pccardd/cardd.c has related code but > it's comment is ``XXX -- dirty hack for some 'ed' cards that have > incomplete iomem CIS tupples.'' > But FreeBSD-current's assign_io function does not have it. This PAO enhancement is dirty hack, but some PC-Card has these broken CIS. So, we need it. Another problem, some PC-Card has non-ascii charactor in CIS Version 1 info. So, -current pccardd can't match pccard.conf of this card. PAO enhace pccardd, can use regex in pccard.conf. I think, "PAO is not best answer. But it is necessary." Is PAO Integration necessary? Yes, some PAO enhancement is very useful and needs in some case. Some patch of PAO, it shuld be merge to -current. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message