From: "White, Charles" <Charles.White@COMPAQ.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] iosapic_vector struct in Linux IA64?
Date: Tue, 24 Oct 2000 19:21:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205618@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205420@msgid-missing>
Great! When is the "next release"?
From: "Mallick, Asit K" <asit.k.mallick@intel.com
<mailto:asit.k.mallick@intel.com> >
To: "'linux-ia64@linuxia64.org'" <linux-ia64@linuxia64.org
<mailto:linux-ia64@linuxia64.org> >
Subject: RE: [Linux-ia64] iosapic_vector struct in Linux IA64?
Date: Tue, 24 Oct 2000 10:48:42 -0700
I have been working on this issue and plan to get the changes incorporated
in the next release.
Thanks,
Asit
> -----Original Message-----
> From: White, Charles [mailto:Charles.White@COMPAQ.com]
<mailto:[mailto:Charles.White@COMPAQ.com]>
> Sent: Monday, October 23, 2000 9:11 AM
> To: 'linux-ia64@linuxia64.org'
> Subject: [Linux-ia64] iosapic_vector struct in Linux IA64?
>
>
> I am looking at an issue with Linux IA64, and the problem
> appears to be that
> the ioapic_vector struct (iosapic.h) has only room for one
> PCI/Bus/Dev/Func/Pin per PID entry...
> Being PCI devices can share interrupts, How do you handle
> that with only one
> Entry? Being even the PIN is part of the entry, you could
> not even tie INTA
> & INTC together.
> Is anyone looking into this issue? Has anyone been working on a
fix?
>
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org <mailto:Linux-IA64@linuxia64.org>
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
<http://lists.linuxia64.org/lists/listinfo/linux-ia64>
>
--__--__--
prev parent reply other threads:[~2000-10-24 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 21:37 [Linux-ia64] iosapic_vector struct in Linux IA64? White, Charles
2000-08-30 22:27 ` Mallick, Asit K
2000-08-31 4:59 ` Takayoshi Kouchi
2000-10-23 16:11 ` White, Charles
2000-10-24 17:48 ` Mallick, Asit K
2000-10-24 19:21 ` White, Charles [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-105590678205618@msgid-missing \
--to=charles.white@compaq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox