From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: adaplas@hotpop.com
Subject: Re: [PATCH] fbdev: Convert MODULE_PARM to module_param in neofb
Date: Fri, 29 Oct 2004 21:35:41 -0700 [thread overview]
Message-ID: <41831A1D.3030901@osdl.org> (raw)
In-Reply-To: <200410292312.i9TNCsDq006882@hera.kernel.org>
Linux Kernel Mailing List wrote:
> ChangeSet 1.2337.1.21, 2004/10/29 13:24:51-07:00, adaplas@hotpop.com
>
> [PATCH] fbdev: Convert MODULE_PARM to module_param in neofb
> Convert MODULE_PARM to module_param in neofb
>
> diff -Nru a/drivers/video/neofb.c b/drivers/video/neofb.c
> @@ -100,18 +100,18 @@
> MODULE_AUTHOR("(c) 2001-2002 Denis Oliver Kropp <dok@convergence.de>");
> MODULE_LICENSE("GPL");
> MODULE_DESCRIPTION("FBDev driver for NeoMagic PCI Chips");
> -MODULE_PARM(internal, "i");
> +module_param(internal, bool, 0);
> MODULE_PARM_DESC(internal, "Enable output on internal LCD Display.");
> -MODULE_PARM(external, "i");
> +module_param(external, bool, 0);
> MODULE_PARM_DESC(external, "Enable output on external CRT.");
> -MODULE_PARM(libretto, "i");
> +module_param(libretto, bool, 0);
> MODULE_PARM_DESC(libretto, "Force Libretto 100/110 800x480 LCD.");
> -MODULE_PARM(nostretch, "i");
> +module_param(nostretch, bool, 0);
> MODULE_PARM_DESC(nostretch,
> "Disable stretching of modes smaller than LCD.");
> -MODULE_PARM(nopciburst, "i");
> +module_param(nopciburst, bool, 0);
> MODULE_PARM_DESC(nopciburst, "Disable PCI burst mode.");
> -MODULE_PARM(mode_option, "s");
> +module_param(mode_option, charp, 0);
> MODULE_PARM_DESC(mode_option, "Preferred video mode ('640x480-8@60', etc)");
Since neofb_setup() still parses options, what does this do?
Provide 2 ways of passing options/arguments?
Same questions for intelfb and i810fb.
Oh, is it this?
neofb_setup() is used for non-modular option parsing,
and module_param() is used for modular or non-modular option parsing.
IOW, using neofb_setup() for option parsing maintains some
backward compatibility for options?
--
~Randy
parent reply other threads:[~2004-10-30 4:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200410292312.i9TNCsDq006882@hera.kernel.org>]
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=41831A1D.3030901@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@hotpop.com \
--cc=linux-kernel@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