9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] tech writer humor
Date: Wed, 23 Feb 2011 09:26:51 -0800	[thread overview]
Message-ID: <AANLkTimxuYyyiiu7bq-t7bPFHx39T7NsGeqDjxi63XtJ@mail.gmail.com> (raw)
In-Reply-To: <601efb4e455d06e4f21af17a0daf8900@ladd.quanstro.net>

On Mon, Feb 21, 2011 at 5:45 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> ah yes, that clears it up
>
>        19.4.22
>        APICID
>        This register uniquely identifies an APIC in the system. This register is not used by
>        OS'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



      parent reply	other threads:[~2011-02-23 17:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22  1:45 erik quanstrom
2011-02-22 17:53 ` ron minnich
2011-02-22 18:22   ` erik quanstrom
2011-02-22 19:20     ` erik quanstrom
2011-02-22 20:09     ` ron minnich
2011-02-22 20:26       ` Devon H. O'Dell
2011-02-22 20:27       ` erik quanstrom
2011-02-22 20:46         ` Nemo
2011-02-22 20:47           ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-02-22 20:54           ` erik quanstrom
2011-02-22 20:57             ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-02-22 21:02               ` erik quanstrom
2011-02-22 21:09                 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-02-23 17:26 ` ron minnich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimxuYyyiiu7bq-t7bPFHx39T7NsGeqDjxi63XtJ@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).