From: Mogens Valentin <monz@danbbs.dk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SATA status report updated
Date: Mon, 22 Aug 2005 00:00:44 +0200 [thread overview]
Message-ID: <4308F98C.8060506@danbbs.dk> (raw)
In-Reply-To: <4308C287.6020603@pobox.com>
Jeff Garzik wrote:
> Mogens Valentin wrote:
>
>> Jeff, is it possible for you at this time to comment on support for
>> the JMicron JMB360 sataII chip? Possible timeframe?
>
> Never heard of it.
Neigher had I. It's being used on the ASrock 939-SATAII mobo, in
conjunction with the ULi M1695 chipset. I wonder why they chose an
unknown SATAII chip for this. The M1695 already has two SATA150
interfaces, and the only test I've seen with SATAII on this mobo used a
SATA150 disk on that JMB360 interface - with poorer results than on the
regular ifc. Could be due to the chip, BIOS, (xp) driver...
The rest of the tests came out pretty good, and the board is well
featured, so naturally I'm interested in possible libata support.
--
Kind regards,
Mogens Valentin
prev parent reply other threads:[~2005-08-21 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 5:09 SATA status report updated Jeff Garzik
2005-08-12 5:40 ` Rob van Nieuwkerk
2005-08-12 5:45 ` Jeff Garzik
2005-08-12 18:07 ` David Greaves
2005-08-12 10:44 ` Matthew Garrett
2005-08-12 21:30 ` Jeff Garzik
2005-08-13 8:45 ` Erik Slagter
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:18 ` Luben Tuikov
2005-08-12 14:46 ` Luben Tuikov
2005-08-12 19:17 ` Mogens Valentin
2005-08-12 19:17 ` Mogens Valentin
[not found] ` <42FCF5D3.1080409@danbbs.dk>
2005-08-12 21:33 ` Jeff Garzik
2005-08-19 8:09 ` Simon Oosthoek
2005-08-21 17:11 ` Mogens Valentin
2005-08-21 18:05 ` Jeff Garzik
2005-08-21 22:00 ` Mogens Valentin [this message]
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=4308F98C.8060506@danbbs.dk \
--to=monz@danbbs.dk \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).