From: Tejun Heo <htejun@gmail.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: [PATCH] libata: Add a drivers/ide style DMA disable
Date: Thu, 20 Sep 2007 10:18:47 +0900 [thread overview]
Message-ID: <46F1CA77.5080102@gmail.com> (raw)
In-Reply-To: <46F145E1.1050107@redhat.com>
Chuck Ebbert wrote:
> On 08/22/2007 06:37 PM, Alan Cox wrote:
>> This is useful when debugging, handling problem systems, or for
>> distributions just to get the system installed so it can be sorted
>> out later.
>>
>> This is a bit smarter than the old IDE one and lets you do
>>
>> libata.pata_dma=0 Disable all PATA DMA like old IDE
>> libata.pata_dma=1 Disk DMA only
>> libata.pata_dma=2 ATAPI DMA only
>> libata.pata_dma=4 CF DMA only
>>
>> (or combinations thereof - 0,1,3 being the useful ones I suspect)
>>
>
> This doesn't help distro installers with modular libata, as there's
> no good way to get the parameter to the driver. (libata.pata_dma=0
> just causes "unrecognized parameter" message on boot.)
Dunno how all those initrd black magics work but SUSE initrd manages to
deliver "module.param" parameters on kernel command line to respective
modules in initrd. I don't think it gets to modules which are loaded
after root is mounted tho.
--
tejun
next prev parent reply other threads:[~2007-09-20 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 22:37 [PATCH] libata: Add a drivers/ide style DMA disable Alan Cox
2007-09-07 3:58 ` Tejun Heo
2007-09-07 22:47 ` Jeff Garzik
2007-09-08 6:01 ` Tejun Heo
2007-09-08 18:42 ` Alan Cox
2007-09-14 17:17 ` Chuck Ebbert
2007-09-14 19:54 ` Bartlomiej Zolnierkiewicz
2007-09-19 15:53 ` Chuck Ebbert
2007-09-19 16:40 ` Alan Cox
2007-09-20 1:18 ` Tejun Heo [this message]
2007-10-02 16:38 ` Jeff Garzik
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=46F1CA77.5080102@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--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 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).