From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LyBrZ-0004rY-UJ
	for qemu-devel@nongnu.org; Sun, 26 Apr 2009 17:26:13 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LyBrU-0004lo-FA
	for qemu-devel@nongnu.org; Sun, 26 Apr 2009 17:26:12 -0400
Received: from [199.232.76.173] (port=48683 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LyBrU-0004lX-99
	for qemu-devel@nongnu.org; Sun, 26 Apr 2009 17:26:08 -0400
Received: from moutng.kundenserver.de ([212.227.126.187]:56089)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <weil@mail.berlios.de>) id 1LyBrT-0003AT-NR
	for qemu-devel@nongnu.org; Sun, 26 Apr 2009 17:26:08 -0400
Message-ID: <49F4D16B.6010700@mail.berlios.de>
Date: Sun, 26 Apr 2009 23:26:03 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Move block format drivers to new directory
	'bdrv'
References: <1240759177-27527-1-git-send-email-avi@redhat.com>	<20090426152943.GA27812@lst.de>
	<49F483E8.4050005@redhat.com>	<f43fc5580904260918n142000e5u1bdf53b6c7b85e32@mail.gmail.com>	<49F489B7.5000705@redhat.com>
	<49F49CB8.2090001@codemonkey.ws>
	<f43fc5580904261110g741a4865ld6d36995514bd18c@mail.gmail.com>
In-Reply-To: <f43fc5580904261110g741a4865ld6d36995514bd18c@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>

Blue Swirl schrieb:
> On 4/26/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>   
>> Avi Kivity wrote:
>>
>>     
>>> Blue Swirl wrote:
>>>
>>>       
>>>> Taking one step further, why not introduce directories similar to
>>>>         
>> VirtualBox:
>>     
>>>> http://www.virtualbox.org/browser/trunk/src/VBox
>>>>
>>>>
>>>>
>>>>         
>>> No objection, but let's go one step at a time.
>>>
>>>       
>>  I was going to suggest exactly the same thing.  It would be good for
>> someone to look at making a more logical layout in hw/.
>>     
>
> hw could be arranged the same way, renamed to 'target':
>
> target
> |-- audio
> |-- block
> |-- bluetooth
> |-- boards
> |   |-- alpha
> |   |-- arm
> |   |-- cris
> |   |-- i386
> |   |-- m68k
> |   |-- mips
> |   |-- ppc
> |   |-- sh4
> |   |-- sparc
> |   |-- sparc64
> |   `-- x86_64
> |-- input
> |-- irq
> |-- isa
> |-- mtd
> |-- net
> |-- pci
> |-- scsi
> |-- serial
> |-- timer
> |-- usb
> |-- video
> `-- xen
>
>
>   

... or similar to linux kernel structure?

target
|-- arch
|   |-- ...
|-- drivers
|   |-- ...


Then it's clearer where the emulation code for a PC board (i386 or x86_64?),
a network card (pci or net?) or others should be placed.