From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <42238e75050e3e65ace758f50a089249@ladd.quanstro.net>
References: <20110706184008.AC595B827@mail.bitblocks.com>
	<CALDPdrpH+G1VS_y5BvwgtmQsb1iLfx_c3VDeM1YeeyqJ6YLxKQ@mail.gmail.com>
	<20110708061922.1CEB3B827@mail.bitblocks.com>
	<856dd0396cfa3bdef849de6d15d42da8@coraid.com>
	<CAP6exYKc4mXGWQi7a06a3tkhDe+z+VCX-z2BhapaSq=ZNYpPJg@mail.gmail.c>
	<42238e75050e3e65ace758f50a089249@ladd.quanstro.net>
Date: Fri,  8 Jul 2011 10:43:06 -0700
Message-ID: <CAP6exYLCR=Ua9Cenv7bDBUvpKT-L1Wsb++E=RJs4dk45vvou_g@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] 9atom & virtualbox 4.0.10 networking issue
Topicbox-Message-UUID: fc436242-ead6-11e9-9d60-3106f5b1d025

On Fri, Jul 8, 2011 at 10:04 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> Why is it not fixed? Because, nowadays, the thing you're supposed to
>> use is the ACPI table. We've seen cases where both PIR and _MP_ were
>> copied from a different motherboard, with no change, and were
>> completely wrong. It's obvious that most vendors don't care to take
>> the time to make these tables right.
>
> so why are acpi tables also broken?

Because, by and large, the vendors don't understand ACPI very well
either, and they tend to just copy and paste.

But it's still the case for me that PIR and MPI are far less reliable than ACPI.

It's why I've gotten to hate PC hardware so much.

ron