From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <601efb4e455d06e4f21af17a0daf8900@ladd.quanstro.net> References: <601efb4e455d06e4f21af17a0daf8900@ladd.quanstro.net> Date: Wed, 23 Feb 2011 09:26:51 -0800 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] tech writer humor Topicbox-Message-UUID: b3ae6c20-ead6-11e9-9d60-3106f5b1d025 On Mon, Feb 21, 2011 at 5:45 PM, erik quanstrom wro= te: > ah yes, that clears it up > > =A0 =A0 =A0 =A019.4.22 > =A0 =A0 =A0 =A0APICID > =A0 =A0 =A0 =A0This register uniquely identifies an APIC in the system. T= his register is not used by > =A0 =A0 =A0 =A0OS'es anymore and is still implemented in hardware because= of FUD. So, my interpretation following the discussions: some over-zealous hardware guy at Intel believes this register is no longer needed because the OS should use BIOS services. Any OS that does not use BIOS services is suffering from FUD, not a real need. I call bull****. The BIOS services work well enough, of course, on most mainboards. Intel mainboards, however, frequently screw the BIOS services and tables up, such that the OS either can not boot or needs to poke around the hardware and use, e.g., this register to find out what's really going on. I'm pretty sure that there is a qualifying instance of irony in here, though I'm relucant to say so since it's an overused term. It's another case of the Intel hardware designer disconnect from the Intel mainboard designers and, following that, Intel's occasional disconnect from reality ... I hit this all the time. (as do others; one person I know was told by Intel that the _MP_ table on his mainboard would get fixed only if the customer was willing to pay for it. Nice.) thanks ron