From: Tejun Heo <tj@kernel.org>
To: Yan Seiner <yan@seiner.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Port multiplier resets
Date: Thu, 20 Nov 2008 12:24:28 +0900 [thread overview]
Message-ID: <4924D86C.8010107@kernel.org> (raw)
In-Reply-To: <4924D733.6070005@seiner.com>
Yan Seiner wrote:
> Tejun Heo wrote:
>>
>> 2. Specify libata.force=8.15:1.5Gbps
>>
> dumb question:
>
> Does this go on the kernel parameter line or can I change it without
> rebooting the system?
>
> I don't see it in /sys/module/libata/parameters so I'm guessing it needs
> a reboot?
Yeah, you will need to reboot or reload libata module. Note that if
libata.ko is being loaded from initrd, different distros use different
methods to pass parameters to them.
--
tejun
next prev parent reply other threads:[~2008-11-20 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 15:10 Port multiplier resets Yan Seiner
2008-11-11 9:06 ` Tejun Heo
2008-11-19 15:15 ` Yan Seiner
2008-11-20 2:27 ` Tejun Heo
2008-11-20 3:05 ` Yan Seiner
2008-11-20 3:23 ` Tejun Heo
2008-11-20 3:19 ` Yan Seiner
2008-11-20 3:24 ` Tejun Heo [this message]
2008-11-22 16:48 ` Yan Seiner
2008-11-23 0:53 ` Tejun Heo
2008-11-25 4:44 ` Yan Seiner
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=4924D86C.8010107@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=yan@seiner.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).