Date: Mon, 30 Jan 2006 09:56:30 -0800
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
Message-ID: <20060130095630.A7765@unix-os.sc.intel.com>
References: <20060130173852.GA16259@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20060130173852.GA16259@kroah.com>; from greg@kroah.com on Mon, Jan 30, 2006 at 09:38:52AM -0800
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1106
Lines: 29

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/