From: Mike Fedyk <mfedyk@matchmail.com>
To: Rumi Szabolcs <rumi_ml@rtfm.hu>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-kernel@vger.kernel.org
Subject: Re: Marvell PATA-SATA bridge meets 2.4.x
Date: Mon, 08 Mar 2004 14:07:43 -0800 [thread overview]
Message-ID: <404CEEAF.5020608@matchmail.com> (raw)
In-Reply-To: <20040308172839.17178753.rumi_ml@rtfm.hu>
Rumi Szabolcs wrote:
> On Sat, 06 Mar 2004 19:55:00 -0800
> Mike Fedyk <mfedyk@matchmail.com> wrote:
>
>
>>Rumi Szabolcs wrote:
>>
>>>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:
>>>
>>>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?
>>
>>You want to use a 2.6 kernel and talk to Bart, and Jeff about this...
>
>
> Well, I don't really want a 2.6 kernel on that machine (yet) because
> in my opinion it is not stable enough for a production system.
What problems are you having?
>
> Would it be hard to fix that in 2.4?
Dunno.
next prev parent reply other threads:[~2004-03-08 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 22:16 Marvell PATA-SATA bridge meets 2.4.x Rumi Szabolcs
2004-03-07 3:55 ` Mike Fedyk
2004-03-08 16:28 ` Rumi Szabolcs
2004-03-08 22:07 ` Mike Fedyk [this message]
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=404CEEAF.5020608@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rumi_ml@rtfm.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.