And in fact, some BIOS vendors purposely run their code through an obfuscator which changes everything to things like ABC9 and XYZ4 or C001, C002, etc.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:acpi-devel- > [EMAIL PROTECTED] On Behalf Of Brown, Len > Sent: Monday, July 25, 2005 10:02 PM > To: Bill Davidsen; Linux Kernel Mailing List > Cc: [EMAIL PROTECTED] > Subject: [ACPI] RE: ACPI oddity > > >On a HT system, why does ACPI recognize CPU0 and CPU1, refer > >to them as such in dmesg > > This is the Linux CPU number. ie the namespace where 0 > is the boot processor and the others are numbered in > the order that they were started. > > > and then call them CPU1 and CPU2 in > >/proc/acpi/processor? > > These are arbitrary device identifiers written > by the BIOS developer and foolishly advertised > to the user by Linux. The BIOS writer could have > also called them ABC9 and XYZ4 and it would be > equally valid. > > We're planning to get rid of all the ACPI stuff > in /proc and move to sysfs. At that time we'll > use device identifies that are deterministic, > like cpu%d that /sys/devices/system uses today. > > cheers, > -Len > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=ick > _______________________________________________ > Acpi-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/acpi-devel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
