From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Mark Lord <liml@rtr.ca>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH #upstream] libata: implement libata.force module parameter
Date: Wed, 20 Feb 2008 12:13:07 -0500 [thread overview]
Message-ID: <47BC5FA3.9050707@garzik.org> (raw)
In-Reply-To: <47B2368D.9080408@gmail.com>
Tejun Heo wrote:
> This patch implements libata.force module parameter which can
> selectively override ATA port, link and device configurations
> including cable type, SATA PHY SPD limit, transfer mode and NCQ.
>
> For example, you can say "use 1.5Gbps for all fan-out ports attached
> to the second port but allow 3.0Gbps for the PMP device itself, oh,
> the device attached to the third fan-out port chokes on NCQ and
> shouldn't go over UDMA4" by the following.
>
> libata.force=2:1.5g,2.15:3.0g,2.03:noncq,udma4
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> Okay, the build failure is dependent on compiler version. 4.1.2 fails
> but 4.2.1 is okay. I was using 4.2.1 so I didn't know about it.
> const is dropped from the offending structure and comment is added.
>
> Documentation/kernel-parameters.txt | 35 +++
> drivers/ata/libata-core.c | 380 +++++++++++++++++++++++++++++++++++-
> drivers/ata/libata-eh.c | 8
> drivers/ata/libata.h | 1
> 4 files changed, 420 insertions(+), 4 deletions(-)
applied
prev parent reply other threads:[~2008-02-20 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 15:14 [PATCH #upstream] libata: implement libata.force module parameter Tejun Heo
2008-02-01 17:28 ` Jeff Garzik
2008-02-01 17:46 ` Bartlomiej Zolnierkiewicz
2008-02-01 18:36 ` Sam Ravnborg
2008-02-08 4:18 ` Tejun Heo
2008-02-12 0:24 ` Tejun Heo
2008-02-12 9:07 ` Tejun Heo
2008-02-12 9:07 ` Tejun Heo
2008-02-13 0:15 ` Tejun Heo
2008-02-13 16:24 ` Mark Lord
2008-02-14 0:17 ` Tejun Heo
2008-02-14 16:24 ` Mark Lord
2008-02-20 17:13 ` Jeff Garzik [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=47BC5FA3.9050707@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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 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.