From: Mike Frysinger <vapier@gentoo.org>
To: Linux-fbdev-devel@lists.sourceforge.net
Subject: [simple patch] touchup virtual frame buffer docs for modules
Date: Wed, 19 Jul 2006 23:04:38 -0400 [thread overview]
Message-ID: <200607192304.39235.vapier@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 212 bytes --]
the Kconfig help text doesnt mention that in order to load the vfb module, you
have to pass in the parameter vfb_enable=1
patch attached to document this and hopefully save someone else some time :)
-mike
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: vfb-module-kconfig-docs.patch --]
[-- Type: text/x-diff, Size: 507 bytes --]
Document required module options in Kconfig for loading the vfb module.
diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
index 6533b0f..6a68a43 100644
--- a/drivers/video/Kconfig
+++ b/drivers/video/Kconfig
@@ -1609,7 +1609,8 @@ config FB_VIRTUAL
kernel option `video=vfb:'.
To compile this driver as a module, choose M here: the
- module will be called vfb.
+ module will be called vfb. In order to load it, you must use
+ the vfb_enable=1 option.
If unsure, say N.
if VT
[-- Attachment #3: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
reply other threads:[~2006-07-20 3:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200607192304.39235.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Linux-fbdev-devel@lists.sourceforge.net \
/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).