qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [PATCH] Compile usb_ohci only for targets that need it


From: Juan Quintela
Subject: [Qemu-devel] Re: [PATCH] Compile usb_ohci only for targets that need it
Date: Wed, 26 Aug 2009 12:15:33 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Gerd Hoffmann <address@hidden> wrote:
> On 08/25/09 20:16, Juan Quintela wrote:
>> It is only needed for arm, ppc and sh4.
>
> Ahem.  It works just fine on a pc too.  And once qdev-ified you can
> even add it via -device.
>
> While it probably makes sense to not build it by default because we
> use uhci for pc I certainly want to have the option to include it.
>
> What is the long-term plan this stuff?  I think it isn't useful to
> hard-code all this in configure.  How about having a
> target-$arch/default-config file with 'CONFIG_FOO=y' lines?  Also look
> for (and prefer if present) a target-$arch/user-config file?
>
> cheers,
>   Gerd

Same thing complained by Anthony yesterday at irc.

Yet knew approach:
a new config-devices.mak file
with a new configuration system: vi/emacs, you select your poison
checking that the configuration is valid:
by now: you try to compile it, and if it works great, if it don't work,
that was a bad configuration.

Will let the creation of tools to a second phase.

1st one is to create a file where all devices are configured for each
target.

Current thing that I am doing is similar to what you propose:

default-configs/<target_name>

<target_name>/config-devices.mak

if it don't exist, it get copied from default-configs/<target_name> one

What do you think?

Later, Juan.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]