| Subject: | Re: Don't buy Foxcon Mboards being sold with dodgy BIOS |
|---|---|
| From: | Big and Blue <No_4@xxxxxxxxxxxxx> |
| Date: | Mon, 28 Jul 2008 19:57:09 +0100 |
| Newsgroups: | uk.comp.os.linux, uk.comp.homebuilt, 24hoursupport.helpdesk |
Nix wrote: (A tiny little bit of research in the topic you're arguing in wouldn't go amiss. A couple of quick searches showed me pages 172--173 of <http://www.acpi.info/DOWNLOADS/ACPIspec30a.pdf> (labelled 154--155) which plainly describe this interface. The diagram on p-4 (pdf p-22) denotes the API Registers/BIOS/Tables interfaces as "OS Independent technologies, interfaces, codes, and hardware". I can't see why it should need to specify an OS setting for this. If it does then it seems to me to be perpetuating what it was trying to stop. However the rest of the document implies that ACPI ("OSPM") can try to work out what it should reply for a particular query based on this setting, though. Seems barmy to me. Why doesn't it just respond with reality and leave it up to the OS decide what to do with the result? Patching an OS is (relatively) simple. Flashing a new BIOS on all motherboards to accommodate each new OS isn't simple. But then, Microsoft is involved, and this means they can blame the hardware manufacturer for any problems.
--
Just because I've written it doesn't mean that
either you or I have to believe it.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Is my old RedHat computer doomed?, Will Kemp |
|---|---|
| Next by Date: | Re: Don't buy Foxcon Mboards being sold with dodgy BIOS, Cork Soaker |
| Previous by Thread: | Re: Don't buy Foxcon Mboards being sold with dodgy BIOS, Nix |
| Next by Thread: | Re: Don't buy Foxcon Mboards being sold with dodgy BIOS, §ñühw¤£f |
| Indexes: | [Date] [Thread] [Top] [All Lists] |