Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262253AbTELQUJ (ORCPT ); Mon, 12 May 2003 12:20:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262269AbTELQUI (ORCPT ); Mon, 12 May 2003 12:20:08 -0400 Received: from havoc.daloft.com ([64.213.145.173]:32698 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id S262253AbTELQUI (ORCPT ); Mon, 12 May 2003 12:20:08 -0400 Date: Mon, 12 May 2003 12:32:49 -0400 From: Jeff Garzik To: linux-kernel@vger.kernel.org Cc: Ivan Kokshaysky , willy@debian.org, davem@redhat.com Subject: Message Signalled Interrupt support? Message-ID: <20030512163249.GF27111@gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 540 Lines: 17 Has anybody done any work, or put any thought, into MSI support? Would things massively break if I set up MSI manually in the driver? I heard rumblings on lkml that Intel has done some work internally w/ MSI support in Linux, but that doesn't help me much without further details ;-) Jeff - 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/