From: Ashok Raj <ashok.raj@intel.com>
To: Greg KH <greg@kroah.com>
Cc: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
Mark Maule <maule@sgi.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>
Subject: Re: FW: MSI-X on 2.6.15
Date: Mon, 30 Jan 2006 09:56:30 -0800 [thread overview]
Message-ID: <20060130095630.A7765@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060130173852.GA16259@kroah.com>; from greg@kroah.com on Mon, Jan 30, 2006 at 09:38:52AM -0800
On Mon, Jan 30, 2006 at 09:38:52AM -0800, Greg KH wrote:
>
> On Mon, Jan 30, 2006 at 10:33:50AM -0600, Miller, Mike (OS Dev) wrote:
> > Greg KH,
> > We have the same results on 2.6.15, the MSI-X table is all zeroes.
> See
> > below. Any ideas of what to do do next? The driver works on x86_64.
> Is
> > there any thing extra I need to do on ia64?
>
> ia64 didn't really have msi support before the latest -mm kernel,
> right
> Mark?
It wasnt enabled in any default configs, but i believe its functional
even earlier. Atleast when i changed the method for irq migration via
/proc, i remember testing on ia64 on ixgb driver.
I havent followed the register_ops() discussion but believe it just changed
the default vector allocation to arch/platform types. But the core
msi should have worked even earlier.
Cheers,
ashok
next prev parent reply other threads:[~2006-01-30 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 16:33 FW: MSI-X on 2.6.15 Miller, Mike (OS Dev)
2006-01-30 16:33 ` Miller, Mike (OS Dev)
2006-01-30 17:38 ` Greg KH
2006-01-30 17:56 ` Ashok Raj [this message]
2006-01-30 19:09 ` Mark Maule
2006-01-30 21:33 ` Roland Dreier
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 20:18 Miller, Mike (OS Dev)
2006-01-30 20:18 ` Miller, Mike (OS Dev)
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=20060130095630.A7765@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=Mike.Miller@hp.com \
--cc=andrew.patterson@hp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maule@sgi.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 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.