Date: Wed, 29 Mar 2006 13:38:00 -0800 From: Nate Lawson <nate@root.org> To: Colin Percival <cperciva@freebsd.org> Cc: Brian Fundakowski Feldman <green@freebsd.org>, src-committers@freebsd.org, cvs-all@freebsd.org, cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/dev/acpica/Osd OsdHardware.c Message-ID: <442AFE38.5090105@root.org> In-Reply-To: <442ADFB7.2010701@freebsd.org> References: <200603290641.k2T6fuMM008597@repoman.freebsd.org> <20060329192230.GH68291@green.homeunix.org> <442ADFB7.2010701@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival wrote: > Brian Fundakowski Feldman wrote: >> On Wed, Mar 29, 2006 at 06:41:56AM +0000, Nate Lawson wrote: >>> Information about this problem was found in Microsoft KB 283649. They >>> block IO accesses if the BIOS indicates via _OSI that it is Windows 2001 >>> or higher. [...] >> Windows 2001 or higher? > > Windows XP was originally going to be called "Windows 2001", but > was renamed at some point after Microsoft sent out information to > hardware manufacturers. Yep. If you want to see the real story of how the OS and system is developed, ACPI is a good window into the nitty gritty. It exposes a lot of information the BIOS knows that isn't documented in the public chipset datasheets. If any committers are interested in helping with ACPI development, I'd be happy to help them get involved. For instance, the eventual migration of cpu frequency control (i.e. SpeedStep) and idle sleep states (C1-3) to servers was telegraphed about a year in advance by changes in the AML code for various motherboards. That's why I spent time getting cpufreq(4) implemented for FreeBSD at that point, not because I am focused on laptops as our main market. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442AFE38.5090105>