From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: [PATCH] allow fb to be a module
Date: Fri, 18 Feb 2005 21:27:12 -0500 [thread overview]
Message-ID: <9e4733910502181827b749aae@mail.gmail.com> (raw)
I split this out into a separate thread. This patch allows fb to be
built as a module. Although James brought up race conditions, I don't
see any upon inspection of the code. The race conditions may have been
from when fbcon was combined into fb. I can believe that fbcon has
race problems. The init/exit functions for fb do the standard things
all device drivers do. This patch makes it much easier to work on fb
since you can make changes without rebooting.
Note that there is a problem with repeated ins/rmmod of radeonfb, but
the problem is in radeonfb not the fb module.
--
Jon Smirl
jonsmirl@gmail.com
diff -Nru a/drivers/video/Kconfig b/drivers/video/Kconfig
--- a/drivers/video/Kconfig 2005-02-17 19:11:37 -05:00
+++ b/drivers/video/Kconfig 2005-02-17 19:11:37 -05:00
@@ -5,7 +5,7 @@
menu "Graphics support"
config FB
- bool "Support for frame buffer devices"
+ tristate "Support for frame buffer devices"
---help---
The frame buffer device provides an abstraction for the graphics
hardware. It represents the frame buffer of some video hardware and
diff -Nru a/drivers/video/Makefile b/drivers/video/Makefile
--- a/drivers/video/Makefile 2005-02-17 19:11:37 -05:00
+++ b/drivers/video/Makefile 2005-02-17 19:11:37 -05:00
@@ -8,11 +8,13 @@
obj-$(CONFIG_LOGO) += logo/
obj-$(CONFIG_SYSFS) += backlight/
-obj-$(CONFIG_FB) += fbmem.o fbmon.o fbcmap.o
fbsysfs.o modedb.o softcursor.o
+obj-$(CONFIG_FB) += fb.o
+fb-y := fbmem.o fbmon.o fbcmap.o
fbsysfs.o modedb.o softcursor.o
# Only include macmodes.o if we have FB support and are PPC
-ifeq ($(CONFIG_FB),y)
-obj-$(CONFIG_PPC) += macmodes.o
+ifneq ($(CONFIG_FB),n)
+fb-$(CONFIG_PPC) += macmodes.o
endif
+fb-objs := $(fb-y)
# Hardware specific drivers go first
obj-$(CONFIG_FB_RETINAZ3) += retz3fb.o
diff -Nru a/drivers/video/fbmem.c b/drivers/video/fbmem.c
--- a/drivers/video/fbmem.c 2005-02-17 19:11:37 -05:00
+++ b/drivers/video/fbmem.c 2005-02-17 19:11:37 -05:00
@@ -1204,7 +1204,22 @@
}
return 0;
}
+
+void __exit
+fbmem_exit(void)
+{
+ class_simple_destroy(fb_class);
+}
+
+#ifdef MODULE
+module_init(fbmem_init);
+module_exit(fbmem_exit);
+MODULE_LICENSE("GPL");
+MODULE_DESCRIPTION("Framebuffer base");
+#else
subsys_initcall(fbmem_init);
+subsys_exitcall(fbmem_exit);
+#endif
static char *video_options[FB_MAX];
static int ofonly;
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
reply other threads:[~2005-02-19 2:27 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=9e4733910502181827b749aae@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).