From: yanh <yanh@lemote.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"Sergei Shtylyov" <sshtylyov@ru.mvista.com>,
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
胡洪兵 <huhb@lemote.com>,
wuzhangjin@gmail.com, linux-mips@linux-mips.org,
"Ralf Baechle" <ralf@linux-mips.org>,
"IDE/ATA development list" <linux-ide@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Philippe Vachon" <philippe@cowpig.ca>,
"Zhang Le" <r0bertz@gentoo.org>,
"Zhang Fuxin" <zhangfx@lemote.com>,
"Arnaud Patard" <apatard@mandriva.com>,
loongson-dev@googlegroups.com, gnewsense-dev@nongnu.org,
"Nicholas Mc Guire" <hofrat@hofr.at>,
"Liu Junliang" <liujl@lemote.com>,
"Erwan Lerale" <erwan@thiscow.com>
Subject: Re: [loongson-PATCH-v1 24/27] fixup for FUJITSU disk
Date: Tue, 26 May 2009 22:39:32 +0800 [thread overview]
Message-ID: <1243348772.9819.77.camel@localhost.localdomain> (raw)
In-Reply-To: <20090526085605.014d0087@lxorguk.ukuu.org.uk>
在 2009-05-26二的 08:56 +0100，Alan Cox写道：
> > > In any case I have yet to see a CS5536 system whose BIOS sets the cable
> > > detection bit. If that's the problem I guess we could add a quirk flag
> > > to override the (lack of) BIOS setting.
> > >
> > This may be the cause that udma5 cannot be set.
>
>
> If the system doesn't have working BIOS cable detect as per the
> documentation for the chip then just return the "unknown" cable type and
> libata will do device side cable detect.
After force cable type as 80 wire, udma5 can be set OK now.
after some raw test, the legacy and native driver have no obvious
difference in performance.
Remain issue: this native driver still have suspend/resume issue.
>
> Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-26 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1242855716.git.wuzhangjin@gmail.com>
2009-05-20 22:12 ` [loongson-PATCH-v1 24/27] fixup for FUJITSU disk wuzhangjin
2009-05-22 18:32 ` Bartlomiej Zolnierkiewicz
2009-05-23 7:11 ` yanh
2009-05-23 11:47 ` Bartlomiej Zolnierkiewicz
2009-05-25 5:45 ` yanh
2009-05-25 7:35 ` 胡洪兵
2009-05-25 14:56 ` Bartlomiej Zolnierkiewicz
2009-05-25 19:05 ` Sergei Shtylyov
2009-05-25 19:10 ` Martin K. Petersen
2009-05-25 19:17 ` Sergei Shtylyov
2009-05-26 1:21 ` yanh
2009-05-26 7:56 ` Alan Cox
2009-05-26 14:39 ` yanh [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=1243348772.9819.77.camel@localhost.localdomain \
--to=yanh@lemote.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apatard@mandriva.com \
--cc=bzolnier@gmail.com \
--cc=erwan@thiscow.com \
--cc=gnewsense-dev@nongnu.org \
--cc=hofrat@hofr.at \
--cc=huhb@lemote.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liujl@lemote.com \
--cc=loongson-dev@googlegroups.com \
--cc=martin.petersen@oracle.com \
--cc=philippe@cowpig.ca \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=sshtylyov@ru.mvista.com \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.com \
/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).