>> [root@antares ~]# grep clocksource dmesg-2.6.17-rc*
>> dmesg-2.6.17-rc1-mm1:Time: tsc clocksource has been installed.
>> dmesg-2.6.17-rc1-mm1:Time: acpi_pm clocksource has been installed.
>> dmesg-2.6.17-rc1-mm2:Time: tsc clocksource has been installed.
>> dmesg-2.6.17-rc1-mm2:Time: acpi_pm clocksource has been installed.
>> dmesg-2.6.17-rc1-mm3:Time: tsc clocksource has been installed.
>> dmesg-2.6.17-rc1-mm3:Time: pit clocksource has been installed.
>> dmesg-2.6.17-rc2-mm1:Time: tsc clocksource has been installed.
>> dmesg-2.6.17-rc2-mm1:Time: pit clocksource has been installed.
>
>Hmmm. I'm not sure why the ACPI PM timer isn't showing up. Your .config
>looks good, but I don't see the ACPI PM timer io-port being detected as
>I expect.
>
>Len, has there been any changes to that ACPI code?
Not that I'm aware of.
Is this issue in -mm only, or does this issue show up in Linus' tree?
Note that there have been 0 integrations from the ACPI tree into
Linus tree during the 2.6.17 cycle, so AFAIK 2.6.17 it should behave
like 2.6.16.
-Len
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]