All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rao, Goutham" <goutham.rao@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Remapping of the IA64 interrupts?
Date: Thu, 26 Oct 2000 17:42:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205635@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205634@msgid-missing>

Hello,
To answer your question... the legacy interrupts need to be re-mapped since
the vectors 0-15 are reserved on IA-64.  
Currently I have a patch that re-maps these interrupts and the PCI
interrupts via a pci_irq_to_vector interface... we will make this patch
available soon.  This may be a solution to the problem you are facing if you
are in fact facing a collision of vectors (PCI to ISA).

Thanks
Goutham
-----Original Message-----
From: White, Charles [mailto:Charles.White@COMPAQ.com]
Sent: Thursday, October 26, 2000 8:23 AM
To: 'linux-ia64@linuxia64.org'
Subject: [Linux-ia64] Remapping of the IA64 interrupts?


I am currently looking at an issue with the ISA interrupts, and it appears
to be caused by the re-mapping of these interrupts. 

From arch/ia64/kernel/irq_ia64.c
----------------------------------------
/*
 * Legacy IRQ to IA-64 vector translation table.  Any vector not in
 * this table maps to itself (ie: irq 0x30 => IA64 vector 0x30)
 */
__u8 isa_irq_to_vector_map[16] = {
	/* 8259 IRQ translation, first 16 entries */
	0x60, 0x50, 0x10, 0x51, 0x52, 0x53, 0x43, 0x54,
	0x55, 0x56, 0x57, 0x58, 0x59, 0x5a, 0x40, 0x41
};
------------------------------------------

Why do this legacy interrupts need to be remapped on the IA64 system?  What
specification did these re-map values come from? 




_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64



      reply	other threads:[~2000-10-26 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26 15:22 [Linux-ia64] Remapping of the IA64 interrupts? White, Charles
2000-10-26 17:42 ` Rao, Goutham [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=marc-linux-ia64-105590678205635@msgid-missing \
    --to=goutham.rao@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.