From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: John Villalovos <jvillalo@redhat.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] Documentation: Add doc about aerdriver.* parameters to kernel-parameters.txt
Date: Fri, 04 Jun 2010 15:34:59 -0700 [thread overview]
Message-ID: <4C097F93.8070109@oracle.com> (raw)
In-Reply-To: <20100604152722.2da5de06.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 2 Jun 2010 11:27:22 -0400
> John Villalovos <jvillalo@redhat.com> wrote:
>
>> Adding documentation about two aerdriver.* command line parameters.
>>
>> Signed-off-by: John L. Villalovos <john.l.villalovos@intel.com>
>>
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index 1808f11..57ff168 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -293,6 +293,19 @@ and is between 256 and 4096 characters. It is defined in the file
>> Format: <io>,<irq>,<dma>,<mss_io>,<mpu_io>,<mpu_irq>
>> See also header of sound/oss/aedsp16.c.
>>
>> + aerdriver.forceload= [HW,PCIE] Advanced Error Recovery (AER) Root Driver
>> + { y, n }
>> + y: Force the AER Root driver to load
>> + n: Do not force the AER Root driver to load [DEFAULT]
>> + See also Documentation/PCI/pcieaer-howto.txt
>> +
>> + aerdriver.nosourceid= [HW,PCIE]
>> + { y, n }
>> + y: Use when broken hardware (mostly chipsets) has root
>> + ports that cannot obtain the reporting source ID.
>> + n: [DEFAULT]
>> + See also Documentation/PCI/pcieaer-howto.txt
>> +
>> agp= [AGP]
>> { off | try_unsupported }
>> off: disable AGP support
>
> We don't normally document the parameters for random drivers within
> kernel-parameters.txt - that file is more for core-kernel things.
>
> The way to document these guys is with MODULE_PARM_DESC() in
> drivers/pci/pcie/aer/aerdrv_core.c. Coz some dope forgot to do that.
>
> I'm sure there's some way of extracting all these random
> MODULE_PARM_DESC()s from vmlinux/modules/etc for human consumption, but
> I'm not sure what that way is.
modinfo <module.ko> does it for one binary module file.
I wrote a script a few years ago that runs 'modinfo *.ko' for all .ko files
that are found in a tree or scans all source files for MODULE_PARM_DESC().
I haven't tested it lately and I don't know of anything "official."
==> http://www.xenotime.net/linux/scripts/module-params
~Randy
prev parent reply other threads:[~2010-06-04 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 15:27 [PATCH] Documentation: Add doc about aerdriver.* parameters to kernel-parameters.txt John Villalovos
2010-06-04 22:27 ` Andrew Morton
2010-06-04 22:34 ` Randy Dunlap [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=4C097F93.8070109@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jvillalo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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).