[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070612073207.GA32646@elte.hu>
Date: Tue, 12 Jun 2007 09:32:07 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Eric St-Laurent <ericstl34@...patico.ca>
Cc: linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Dinakar Guniguntala <dino@...ibm.com>,
Venki Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: v2.6.21.4-rt11
(Cc:-ed Venki for the force-hpet issue below)
* Eric St-Laurent <ericstl34@...patico.ca> wrote:
> On Sat, 2007-09-06 at 23:05 +0200, Ingo Molnar wrote:
> > i'm pleased to announce the v2.6.21.4-rt11 kernel, which can be
> > downloaded from the usual place:
>
> I'm running 2.6.21.4-rt12-cfs-v17 (x86_64), so far no problems. I like
> this kernel a lot, it's feels quite smooth.
yeah, that's probably CFS in the works :-) That combined with PREEMPT_RT
makes for a really snappy desktop.
> One little thing, no HPET timer is detected. By looking at the patch,
> even the force detect code is there, it should work.
>
> The hpet timer is not available as a clocksource and only one hpet
> related message is present in dmesg:
>
> PM: Adding info for No Bus:hpet
>
> This is on a Asus P5LD2-VM motherboard (ICH7)
>
> Relevant config bits:
>
> CONFIG_HPET_TIMER=y
> # CONFIG_HPET_EMULATE_RTC is not set
> CONFIG_HPET=y
> # CONFIG_HPET_RTC_IRQ is not set
> CONFIG_HPET_MMAP=y
>
> Should I enable one of the two other options? Any ideas?
Venki, is this ICH7 board supposed to work with force-hpet?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists