From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] entry->irq = entry->link.index (problem 2 of thread [ Re: patch for updating IA64 A
Date: Mon, 23 Jun 2003 18:27:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105639307615971@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105635248609013@msgid-missing>
>>>>> On Mon, 23 Jun 2003 15:13:18 +0800, "Yu, Luming" <luming.yu@intel.com> said:
>> @@ -248,6 +253,8 @@
>> return_VALUE(0);
>> }
>> + entry->irq = entry->link.index;
>> +
>> if (!entry->irq && entry->link.handle) {
entry-> irq = acpi_pci_link_get_irq(entry->link.handle, entry->link.index);
>> if (!entry->irq) {
>> I don't quite understand what this is for. Anyone know?
Luming> To understand the meaning of entry->link.index, please
Luming> reference acpi_get_prt which is in arch/ia64/kernel/acpi.c.
Luming> There is vector[i].irq = entry->link.index , entry is
Luming> acpi_prt_entry. And you can look into mp_parse_prt which is
Luming> in arch/i386/kernel/mpparse.c. There is irq Luming> entry->link.index.
Ah, that's where x86 is doing the transformation. Thanks for finding
that. I didn't understand how the old code worked on x86.
Can we do the transformation at the same time on both platforms?
Obviously there is no mpparse.c but perhaps arch/ia64/kernel/acpi.c
could do it. I wonder though if this scheme would work with hotplug
devices.
In any case, whatever the solution, we clearly should use the same
approach on both platforms.
--david
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
prev parent reply other threads:[~2003-06-23 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 7:13 [Linux-ia64] entry->irq = entry->link.index (problem 2 of thread [ Re: patch for updating IA64 ACPI Yu, Luming
2003-06-23 18:27 ` David Mosberger [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-105639307615971@msgid-missing \
--to=davidm@napali.hpl.hp.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.