Date: Wed, 26 Feb 2003 00:11:37 -0500 From: "Brian F. Feldman" <green@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/pccard/pccardc Makefile dumpcisfile.c pccardc.8 pccardc.c src/usr.sbin/pccard/pccardd readcis.c readcis.h Message-ID: <200302260511.h1Q5Bbxw012540@green.bikeshed.org> In-Reply-To: Your message of "Tue, 25 Feb 2003 21:58:08 MST." <20030225.215808.87764783.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" <imp@bsdimp.com> wrote: > I plan on having a pccard/cardbus utility that will do dumpcis > functionality. The input can come from hardware or a file. It can > output binary or text file. I also thought about having a CIS > compiler that would take the output of the dumpcis and produce a > binary. I was also planning on expanding the pccard/cardbus CIS quirk > stuff so that it could be loaded from a file (maybe even at boot > time). > > Note: the output format would be different than the current dumpcis > format. > > Linux has something very similar (or so I've been lead to believe from > indirect evidence). If it has a suitable license, I may just use it. That sounds like a cool plan :-) The Linux utilities are crap; they're intensely machine-dependent. For example, the CIS-to-text utility uses special calls to the kernel to have it parse the CIS and give it back in a different format, doing most of the work. I haven't looked at the compiler, but I don't think it would be hard at all to do. Come to think of it, I bet we could reuse Iwasaki-san's amldb code, and teach it to use CIS instead of DSDT. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302260511.h1Q5Bbxw012540>