Date: Wed, 25 Sep 2002 09:38:07 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: dave@dogwood.com Cc: grog@FreeBSD.org, jhb@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf files.i386 src/sys/i386/i386 legacy.c src/sys/i386/include legacyvar.h Message-ID: <20020925.093807.04037851.imp@bsdimp.com> In-Reply-To: <200209250531.g8P5VOdw083783@white.dogwood.com> References: <20020923.201300.80213923.imp@bsdimp.com> <200209250531.g8P5VOdw083783@white.dogwood.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <200209250531.g8P5VOdw083783@white.dogwood.com>
Dave Cornejo <dave@dogwood.com> writes:
: A stupid minor nit - Is there a better word than 'legacy' since it's
: relative? One day ACPI will be a legacy also.
well, it really means 'some ad-hoc cobbled together set of proceedures
to enumerate devices that aren't in some plug and play table' which
can apply to all architectures. :-) 'legacy' is just a way of saying
'the nexus has to have special knowledge of these things, and have a
lot of hacks to keep the various methods from interferring.' Since
there never was a name for this mess, and since the problem can exist
on multiple architectures, I think legacy is about as good as we are
going to get.
Warner
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?20020925.093807.04037851.imp>