Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758186AbYHKX6w (ORCPT ); Mon, 11 Aug 2008 19:58:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758459AbYHKX6B (ORCPT ); Mon, 11 Aug 2008 19:58:01 -0400 Received: from mga09.intel.com ([134.134.136.24]:53025 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758172AbYHKX6A (ORCPT ); Mon, 11 Aug 2008 19:58:00 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.32,192,1217833200"; d="scan'208";a="428332827" From: Seth Heasley To: jgarzik@pobox.com, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 2.6.26.2][RESEND] ahci: RAID mode SATA patch for Intel Ibex Peak DeviceIDs Date: Mon, 11 Aug 2008 17:03:09 -0700 User-Agent: KMail/1.9.1 Cc: seth.heasley@intel.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200808111703.09743.seth.heasley@intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 23 Resend with proper whitespace. This patch adds the Intel Ibex Peak (PCH) SATA RAID Controller DeviceIDs. Signed-off-by: Seth Heasley --- linux-2.6.26.2/drivers/ata/ahci.c.orig 2008-08-08 11:34:48.000000000 -0700 +++ linux-2.6.26.2/drivers/ata/ahci.c 2008-08-08 11:36:06.000000000 -0700 @@ -445,6 +445,8 @@ { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */ { PCI_VDEVICE(INTEL, 0x3a05), board_ahci }, /* ICH10 */ { PCI_VDEVICE(INTEL, 0x3a25), board_ahci }, /* ICH10 */ + { PCI_VDEVICE(INTEL, 0x3b24), board_ahci }, /* PCH RAID */ + { PCI_VDEVICE(INTEL, 0x3b2b), board_ahci }, /* PCH RAID */ /* JMicron 360/1/3/5/6, match class to avoid IDE function */ { PCI_VENDOR_ID_JMICRON, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, -- 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/