From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53216)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agarcia@igalia.com>) id 1VL9op-0003Fm-0X
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 06:44:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <agarcia@igalia.com>) id 1VL9oh-0008GP-MF
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 06:44:42 -0400
Received: from smtp3.mundo-r.com ([212.51.32.191]:31748 helo=smtp4.mundo-r.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agarcia@igalia.com>) id 1VL9oh-0008BY-FP
	for qemu-devel@nongnu.org; Sun, 15 Sep 2013 06:44:35 -0400
Date: Sun, 15 Sep 2013 12:43:57 +0200
From: Alberto Garcia <agarcia@igalia.com>
Message-ID: <20130915104357.GA16613@igalia.com>
References: <1377471536-12423-1-git-send-email-akoskovacs@gmx.com>
	<1377471536-12423-22-git-send-email-akoskovacs@gmx.com>
	<521B316E.6070703@redhat.com> <521B8D3E.4080106@suse.de>
	<521BD95F.4030708@redhat.com> <52331A60.9020400@suse.de>
	<5233260C.4080608@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5233260C.4080608@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 21/47] hw/char/Kconfig: Add Kconfig file
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: =?iso-8859-1?Q?=C1kos_Kov=E1cs?= <akoskovacs@gmx.com>, Andreas =?iso-8859-1?Q?F=E4rber?= <afaerber@suse.de>, qemu-devel@nongnu.org

On Fri, Sep 13, 2013 at 04:49:48PM +0200, Paolo Bonzini wrote:

> I'm not sure of the benefit of an hw/ipack directory if (a) there is
> only one class providing the bus and (b) all the classes using the
> bus (well, there is just one of them) are in the same directory.
> 
> If any of the two conditions were not true anymore, I'd ask to
> contextually create hw/ipack.  But for now, keeping both ipack files
> in hw/char is the most "economic" thing to do.

I decided to emulate both boards separately because it was not much
more work and it seemed like a better idea to me, but it was the
tpci200/ipoctal combination that I was interested in.

So it sounds reasonable to me to keep both files together.

Berto