[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6b4e42d10610271531w51ec107s881389a9b541dbff@mail.gmail.com>
Date: Fri, 27 Oct 2006 15:31:32 -0700
From: "Om Narasimhan" <om.turyx@...il.com>
To: "Mika Penttilä" <mika.penttila@...umbus.fi>
Cc: "Vojtech Pavlik" <vojtech@...e.cz>, "Andi Kleen" <ak@....de>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
linux-kernel@...r.kernel.org, randy.dunlap@...cle.com,
clemens@...isch.de, bob.picco@...com
Subject: Re: HPET : Legacy Routing Replacement Enable - 3rd try.
> >
> >
> There seems to be lot of confusion here. Current code isn't using hpet
> as tick source if legacy is not supported. This patch adds
> hpet_lrr_force but it's not clear how it interacts with hpet_use_timer -
> in some places it is hpet_use_timer and some (hpet_use_timer &&
> hpet_lrr_force).
>
> The timer is routed to ioapic pin 2 which is irq0 with source override.
> With this patch with hpet_lrr_force=1 timer irq is set to 2 for x86_64
> and 0 for i386, that can't be right?
Hmm... if hpet_lrr_force=1, timer irq should be set to 2 both in
x86_64 as well as i386.
This is my mistake. I should test more thoroughly :-(
Thanks for comments.
Om.
>
> --Mika
>
>
>
-
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