From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ILgq3-0007Wa-0i for qemu-devel@nongnu.org; Thu, 16 Aug 2007 11:00:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ILgq0-0007V6-QZ for qemu-devel@nongnu.org; Thu, 16 Aug 2007 11:00:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ILgq0-0007V3-Lm for qemu-devel@nongnu.org; Thu, 16 Aug 2007 11:00:40 -0400 Received: from nz-out-0506.google.com ([64.233.162.236]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ILgq0-0000f5-87 for qemu-devel@nongnu.org; Thu, 16 Aug 2007 11:00:40 -0400 Received: by nz-out-0506.google.com with SMTP id f1so416217nzc for ; Thu, 16 Aug 2007 08:00:39 -0700 (PDT) Message-ID: <46C46693.1020307@freeshell.org> Date: Thu, 16 Aug 2007 11:00:35 -0400 From: "Bill C. Riemers" MIME-Version: 1.0 Subject: Re: [Qemu-devel] merging kqemu into mainline kernel? References: <8a6cde920708040926s6e12edd0mc3b469ab741c5653@mail.gmail.com> <23bcb8700708160542m45c3d561q3c1590fcfeea3a09@mail.gmail.com> <46C448DA.70303@gmail.com> In-Reply-To: <46C448DA.70303@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: Doctor Bill Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dragoran Cc: qemu-devel@nongnu.org dragoran wrote: > Bill C. Riemers wrote: >> You don't need to compile kqemu into the kernel. When I install >> dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly >> certain with Fedora's new policy for extras, there would not be much >> of a problem getting it added to Fedora. For that matter, it could >> probably get added into the new Enterprise Extra's repository as >> well. However, someone would need to volunteer to maintain the package. > no thats not true fedora want to change the policy about out of tree > modules the want to drop all kmod-* packages and only allow modules > into the kernel rpm that are upstream or about to get merged upstream. > anyway why has kqemu to be a out of tree module? It looks like you are right. Apparently the plan is to move the acceptance of kernel modules to kernel maintainers. For the most part, they only want to accept very cleanly written modules that are likely to be integrated into the kernel. Since "kqemu" is viewed as a solution only for obsolete hardware, that is not likely to happen. It is a shame too, because "kqemu" provides a quality working solution for most of the hardware still in use today. Bill