From: Andi Kleen <ak@suse.de>
To: "Om Narasimhan" <om.turyx@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HPET : timer routing setup with Legacy Routing Replacement bit set
Date: 27 Sep 2006 21:56:59 +0200 [thread overview]
Message-ID: <p73ac4ljd6c.fsf@verdi.suse.de> (raw)
In-Reply-To: <6b4e42d10609271046x216e5175g59cb42f12e067c82@mail.gmail.com>
"Om Narasimhan" <om.turyx@gmail.com> writes:
> Hi,
> I am working with a new bios for a server our company build. I am
> confused about the routing of the timer and arch/x86_64/kernel/time.c
> irq setup.
>
> HPET specification states that if Legacy routing replacement enable
> bit is set, IRQ0 should not be connected to PIN0 of IOAPIC, and IRQ0
> should not generate any interrupts. But in the kernel code, timer is
> hard coded to irq0 (arch/x86_64/kernel/time.c : time_init(), calls
> setup_irq(0,&irq0). 0 being the irq number)
>
> My question is, should it not be IRQ2 if HPET is enabled and Legacy
> Routing Replacement bit is enbaled?
Legacy Routing Replacement is currently not supported.
Feel free to contribute a patch supporting it though.
-Andi
prev parent reply other threads:[~2006-09-27 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 17:46 HPET : timer routing setup with Legacy Routing Replacement bit set Om Narasimhan
2006-09-27 19:56 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73ac4ljd6c.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=om.turyx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox