From: Rumi Szabolcs <rumi_ml@rtfm.hu>
To: linux-kernel@vger.kernel.org
Subject: Marvell PATA-SATA bridge meets 2.4.x
Date: Fri, 5 Mar 2004 23:16:42 +0100 [thread overview]
Message-ID: <20040305231642.708841dd.rumi_ml@rtfm.hu> (raw)
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
next reply other threads:[~2004-03-05 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 22:16 Rumi Szabolcs [this message]
2004-03-07 3:55 ` Mike Fedyk
2004-03-08 16:28 ` Rumi Szabolcs
2004-03-08 22:07 ` Mike Fedyk
2004-03-08 23:53 ` Rumi Szabolcs
2004-03-09 4:06 ` Mike Fedyk
2004-03-11 7:20 ` Andre Hedrick
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=20040305231642.708841dd.rumi_ml@rtfm.hu \
--to=rumi_ml@rtfm.hu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®