On Mon, 2013-07-29 at 13:27 +0200, Paolo Bonzini wrote:
> Il 29/07/2013 10:00, Marcel Apfelbaum ha scritto:
> > On Mon, 2013-07-29 at 09:36 +0200, Paolo Bonzini wrote:
> >> Il 28/07/2013 11:14, Marcel Apfelbaum ha scritto:
> >>> Categories:
> >>> Assembly - hosts/hubs/...
> >>
> >> A lot of these
Il 29/07/2013 10:00, Marcel Apfelbaum ha scritto:
> On Mon, 2013-07-29 at 09:36 +0200, Paolo Bonzini wrote:
>> Il 28/07/2013 11:14, Marcel Apfelbaum ha scritto:
>>> Categories:
>>> Assembly - hosts/hubs/...
>>
>> A lot of these seem to fit in a "bridge" category.
> I wanted to group in a category
On Mon, 2013-07-29 at 09:36 +0200, Paolo Bonzini wrote:
> Il 28/07/2013 11:14, Marcel Apfelbaum ha scritto:
> > Categories:
> > Assembly - hosts/hubs/...
>
> A lot of these seem to fit in a "bridge" category.
I wanted to group in a category as much as possible having in
mind the user shall "grep
Il 28/07/2013 11:14, Marcel Apfelbaum ha scritto:
> Categories:
> Assembly - hosts/hubs/...
A lot of these seem to fit in a "bridge" category.
I'm not sure why usbhost is in the assembly category though. Also, why
is this the default category for isa and i2c devices?
> Management - controller
On Sun, Jul 28, 2013 at 12:14:52PM +0300, Marcel Apfelbaum wrote:
> Running qemu with "-device ?" option returns ~145 lines.
> It is hard to manage understanding the output.
>
> Theses patches aim to partially solve the problem by dividing the devices
> into logical categories like "Network/Displa
Running qemu with "-device ?" option returns ~145 lines.
It is hard to manage understanding the output.
Theses patches aim to partially solve the problem by dividing the devices
into logical categories like "Network/Display/..." and sorting them by it.
Categories:
Assembly - hosts/hubs/...
Mana
