From: "Jerome Pinot" <ngc891@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] kqemu 0.7.2
Date: Thu, 30 Mar 2006 08:05:03 -0000 [thread overview]
Message-ID: <88ee31b70603300004q52694f88s6c19c235bb8cb5a@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Hi,
Well, I know there is ongoing work on the next release of kqemu, but I
thought it could be useful to get the stable release still work with
the current linux kernel.
MODULE_PARM shouldn't be used anymore. This patch makes kqemu compiled
with recent kernel.
If the patch is broken (thanks to gmail), you can find it here too:
http://ngc891.blogdns.net/pub/projects/patches/kqemu-0.7.2-module_param.diff
BTW, it could worth it to add something like:
---
If you're using udev, you can add a rule to have the device node
created automaticaly when you load the kqemu module, for example:
# echo 'KERNEL="kqemu", NAME="%k", MODE="0666"' >
/etc/udev/rules.d/30-kqemu.rules
---
in the Linux installation part of the documentation.
Regards,
--
Jerome Pinot
http://ngc891.blogdns.net/
[-- Attachment #2: kqemu-0.7.2-module_param.diff --]
[-- Type: application/octet-stream, Size: 598 bytes --]
diff -Naur kqemu/kqemu-linux.c kqemu-mod/kqemu-linux.c
--- kqemu/kqemu-linux.c 2005-09-03 16:39:36.000000000 +0000
+++ kqemu-mod/kqemu-linux.c 2006-03-30 07:26:20.000000000 +0000
@@ -48,11 +48,11 @@
/* if 0 is used, then devfs/udev is used to automatically create the
device */
int major = 250;
-MODULE_PARM(major,"i");
+module_param(major, int, 0);
/* configurable max_instances */
int max_instances = 4;
-MODULE_PARM(max_instances,"i");
+module_param(max_instances, int, 0);
/* lock the page at virtual address 'user_addr' and return its
page index. Return -1 if error */
reply other threads:[~2006-03-30 8:05 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=88ee31b70603300004q52694f88s6c19c235bb8cb5a@mail.gmail.com \
--to=ngc891@gmail.com \
--cc=qemu-devel@nongnu.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).