Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261298AbUCEWQr (ORCPT ); Fri, 5 Mar 2004 17:16:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261313AbUCEWQr (ORCPT ); Fri, 5 Mar 2004 17:16:47 -0500 Received: from quasar.dynaweb.hu ([195.70.37.87]:45726 "EHLO quasar.dynaweb.hu") by vger.kernel.org with ESMTP id S261298AbUCEWQp (ORCPT ); Fri, 5 Mar 2004 17:16:45 -0500 Date: Fri, 5 Mar 2004 23:16:42 +0100 From: Rumi Szabolcs To: linux-kernel@vger.kernel.org Subject: Marvell PATA-SATA bridge meets 2.4.x Message-Id: <20040305231642.708841dd.rumi_ml@rtfm.hu> X-Mailer: Sylpheed version 0.9.6 (GTK+ 1.2.10; sparc-sun-solaris2.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1550 Lines: 37 Hello! A while ago I reported a problem with the 2.4.22 kernel and the tiny Marvell PATA to SATA bridge chip that is used on many of the now-not-so-recent motherboards which don't have native SATA ports in their southbridges. As it can be seen below, a native SATA150 drive is connected to a SATA port implemented using that Marvell chip hooked up to the ICH4's parallel ATA133 port and this way the drive is only recognized (and used) as UDMA33: ICH4: IDE controller at PCI slot 00:1f.1 ICH4: chipset revision 2 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio hdc: ST3160023AS, ATA DISK drive blk: queue c04a1ff4, I/O limit 4095Mb (mask 0xffffffff) ide1 at 0x170-0x177,0x376 on irq 15 hdc: attached ide-disk driver. hdc: host protected area => 1 hdc: 312581808 sectors (160042 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(33) As far as I can remember someone (Jeff Garzik?) suspected the SATA cable not being recognized as a 80-conductor thus >=UDMA66 capable cable. Then it was told that there is a fix underway that will be included in the 2.4.23 kernel. The above snippet shows that the 2.4.25 kernel still has this problem. Any comments? Regards, Szabolcs Rumi - 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/