From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41826) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLNUz-0008OC-2x for qemu-devel@nongnu.org; Tue, 01 Nov 2011 19:12:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLNUx-0005tg-Pb for qemu-devel@nongnu.org; Tue, 01 Nov 2011 19:12:05 -0400 Received: from nskntmtas04p.mx.bigpond.com ([61.9.168.146]:52780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLNUx-0005tH-BZ for qemu-devel@nongnu.org; Tue, 01 Nov 2011 19:12:03 -0400 Message-ID: <4EB07CBB.5020008@rtems.org> Date: Wed, 02 Nov 2011 10:11:55 +1100 From: Chris Johns MIME-Version: 1.0 References: <4639B135-B96A-43A0-B4FA-6DDCBE3FBA92@suse.de> <4EAFC479.1090601@redhat.com> In-Reply-To: <4EAFC479.1090601@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Peter Maydell , Alexander Graf , "qemu-devel@nongnu.org Developers" On 1/11/11 9:05 PM, Gerd Hoffmann wrote: > Adding a > device is simply a matter of dropping a file into the tree and a line > into the Makefile and you are done. The device is available to be used > via -device. So the cost of maintaining stuff out-of-tree isn't that > big as you almost never have patch conflict issues. > The concern here is when something goes wrong. A user who does not know qemu's source picks up the source for a driver they would like to use how-ever the qemu they build does not work as they expect. With a binary blob they question their set up or options, with something they build there is more doubt about the nature of the failure. Chris