From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] tech writer humor
Date: Tue, 22 Feb 2011 14:20:40 -0500 [thread overview]
Message-ID: <95acb22e4c0cec7d7a4490ff738fa2ce@coraid.com> (raw)
In-Reply-To: <e8888e046d6af4ac7f84ec61882b1f75@coraid.com>
> > > 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.
> > >
> > > (Intel® 5520 chipset and Intel® 5500 chipset datasheet pub 321328)
> >
> > Did intel claim that the OSes should be using ACPI? What do they use instead?
> >
> > ron
> > p.s. I appreciate the humor but it does lead to a serious question.
>
> afik, acpi has nothing to do with this problem. i believe this particular
> tech writer intends to claim that nobody uses physical addressing anymore.
> but i believe bios still needs to use physical addressing before logical addressing
> is established. so i think the writer may be speaking a misleading half
> of the whole story.
i think i was unclear. by physical vs. logical addressing i mean of course of
the various system apics, not of memory.
in any event, the logical addressing is the responsibility of the os, so acpi
doesn't provide it either. (annoying how acpi and apic obvious anagrams.)
- erik
next prev parent reply other threads:[~2011-02-22 19:20 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 [this message]
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
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=95acb22e4c0cec7d7a4490ff738fa2ce@coraid.com \
--to=quanstro@labs.coraid.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).