RE: [ACPI] RE: ACPI oddity

[Moore, R. <rob...@in...>]

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: acp...@li... [mailto:acpi-devel-
> ad...@li...] On Behalf Of Brown, Len
> Sent: Monday, July 25, 2005 10:02 PM
> To: Bill Davidsen; Linux Kernel Mailing List
> Cc: acp...@li...
> Subject: [ACPI] RE: ACPI oddity
>=20
> >On a HT system, why does ACPI recognize CPU0 and CPU1, refer
> >to them as such in dmesg
>=20
> 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.
>=20
> > and then call them CPU1 and CPU2 in
> >/proc/acpi/processor?
>=20
> 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.
>=20
> 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.
>=20
> cheers,
> -Len
>=20
>=20
> -------------------------------------------------------
> 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_id=16492&op=3Dick
> _______________________________________________
> Acpi-devel mailing list
> Acp...@li...
> https://lists.sourceforge.net/lists/listinfo/acpi-devel