Date: Tue, 24 Sep 2002 23:20:57 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: Dave Cornejo <dave@dogwood.com> Cc: "M. Warner Losh" <imp@bsdimp.com>, 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: <20020924232057.B89090@FreeBSD.org> In-Reply-To: <200209250531.g8P5VOdw083783@white.dogwood.com>; from dave@dogwood.com on Tue, Sep 24, 2002 at 10:31:24PM -0700 References: <20020923.201300.80213923.imp@bsdimp.com> <200209250531.g8P5VOdw083783@white.dogwood.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Dave Cornejo <dave@dogwood.com> [ Data: 2002-09-24 ] [ Subjecte: Re: cvs commit: src/sys/conf files.i386 src/sys/i386/i386 legacy.c src/sys/i386/include legacyvar.h ] > A stupid minor nit - Is there a better word than 'legacy' since it's > relative? One day ACPI will be a legacy also. x86 has already overstayed its welcome, let's hope it disappears before that's the case. The problem is we have a lot of mostly similar architectures based around what evolved from the AT systems, but no general term. ACPI will always be ACPI. legacy in this case is a bunch of legacy stuff which is fairly similar. ACPI will be ACPI. Period. There's no real configuration methods in the legacy architecture, not like ACPI provides, so ACPI will stay ACPI, while legacy refers to the first generation of x86 systems that FreeBSD supported. -- Juli Mallett <jmallett@FreeBSD.org> | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! 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?20020924232057.B89090>