From: Juan Quintela <quintela@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Compile usb_ohci only for targets that need it
Date: Wed, 26 Aug 2009 12:15:33 +0200 [thread overview]
Message-ID: <m3fxbe6fui.fsf@neno.mitica> (raw)
In-Reply-To: <4A9508AC.5070205@redhat.com> (Gerd Hoffmann's message of "Wed, 26 Aug 2009 12:04:28 +0200")
Gerd Hoffmann <kraxel@redhat.com> 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.
next prev parent reply other threads:[~2009-08-26 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:16 [Qemu-devel] [PATCH] Compile usb_ohci only for targets that need it Juan Quintela
2009-08-26 10:04 ` Gerd Hoffmann
2009-08-26 10:13 ` [Qemu-devel] " Juan Quintela
2009-08-26 10:15 ` Juan Quintela [this message]
2009-08-26 10:28 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fxbe6fui.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).