On 4 June 2013 12:04, Peter Maydell wrote:
> You don't need to do this, because there are no config files
> in default-configs/ for these, so this patch set will not
> change the behaviour for them.
Oh, my apologies; I tested the bsd-user WIP at some point in the past,
and it seems I have arm- an
On 4 June 2013 16:27, Ed Maste wrote:
> On 20 May 2013 19:09, Peter Maydell wrote:
>> I'm not sure that's worth the effort at this point when we don't
>> actually have any targets in tree which aren't enabled by default,
>> though. (I did cross-check the old and new lists so this patch
>> isn't a
On 20 May 2013 19:09, Peter Maydell wrote:
> I'm not sure that's worth the effort at this point when we don't
> actually have any targets in tree which aren't enabled by default,
> though. (I did cross-check the old and new lists so this patch
> isn't accidentally enabling a previously disabled co
On 20 May 2013 22:11, Andreas Färber wrote:
> Am 20.05.2013 17:16, schrieb Peter Maydell:
>> Autogenerate the default target list based on what files exist
>> in default-configs; this allows us to remove one of the places
>> that has to be kept up to date with a complete list of every
>> target we
Am 20.05.2013 17:16, schrieb Peter Maydell:
> Autogenerate the default target list based on what files exist
> in default-configs; this allows us to remove one of the places
> that has to be kept up to date with a complete list of every
> target we support.
>
> Signed-off-by: Peter Maydell
In th
Autogenerate the default target list based on what files exist
in default-configs; this allows us to remove one of the places
that has to be kept up to date with a complete list of every
target we support.
Signed-off-by: Peter Maydell
---
configure | 84 +++-
