qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>, qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Deprecate the "collie" machine and Strongarm devices
Date: Mon, 29 Oct 2018 23:17:06 +0100	[thread overview]
Message-ID: <034785b2-0126-e480-2f3f-2295152b11ae@redhat.com> (raw)
In-Reply-To: <20181029202450.GB24689@roeck-us.net>

On 29/10/18 21:24, Guenter Roeck wrote:
> On Mon, Oct 29, 2018 at 04:03:40PM +0100, Philippe Mathieu-Daudé wrote:
>> On 29/10/18 15:09, Guenter Roeck wrote:
>>> On 10/29/18 6:24 AM, Peter Maydell wrote:
>>>> On 27 October 2018 at 12:04, Guenter Roeck <linux@roeck-us.net> wrote:
>>>>> On 10/26/18 3:12 AM, Peter Maydell wrote:
>>>>>> Hi Guenter; there's a proposal here to deprecate (and eventually
>>>>>> remove) the 'collie' board (strongarm) from QEMU. Is that one of
>>>>>> the ones you're currently using in your automated testing of Linux
>>>>>> kernels on QEMU?
>>>>>>
>>>>>
>>>>> Yes. I can run the test with older versions of qemu, so it is ok for me
>>>>> if it is removed (as long as that removal is not backported).

[...]

>>> Though not all of them are supported by upstream qemu. For some of them I
>>> carry local patches,
>>> for others I use out-of-tree versions of qemu (beagle/beaglexm).
>>
>> Are these patches upstream-able?
>>
> 
> Some of the patches (eg to be able to boot a Linux kernel image for mps2-an385
> directly from qemu, or zynq CPU clock rate changes to be able to do the same)
> have been rejected. A few patches were submitted at some point but got lost.
> I don't keep track, so I don't know the exact number. For some patches, such
> as basic BCM283x CPRMAN support (needed to boot raspi2), a better
> implementation was suggested, but didn't go anywhere as far as I know.
> 
> Some machines, such as beagle support, are from Linaro's tree and were never
> upstreamed by Linaro. The Linaro branch is based off qemu 2.3, so applying
> the changes to upstream qemu would be a major effort. I also use the m68k
> branch from github.com:vivier/qemu-m68k.git for m68k tests.
> 
> I carry some 20+ patches locally in my qemu tree. Some may be obsolete or
> not or no longer needed (my understanding of qemu is evolving). Sometimes,
> if and when I find the time, I pick some and try to upstream, but I often
> don't follow up if there is no response or if the requested changes are
> too substantial.
> 
> Please feel free to have a look at https://github.com/groeck/qemu
> (check the <version>-local branches) and let me know what might be
> upstreamable. I'll be happy to (re-)submit the respective patches.
> Note that I won't be able to make any substantial changes, though.
> Time is a scarce commodity nowadays, unfortunately.

Thank you for pointing your work, I'll try to salvage what I can.

Regards,

Phil.

  reply	other threads:[~2018-10-29 22:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 10:06 [Qemu-devel] [PATCH 0/2] Deprecate the "collie" machine and Strongarm devices Thomas Huth
2018-10-26 10:06 ` [Qemu-devel] [PATCH 1/2] hw/arm: Deprecate the "collie" board Thomas Huth
2018-10-26 10:06 ` [Qemu-devel] [PATCH 2/2] arm: Deprecate the Strongarm sa1100 and sa1110 processors Thomas Huth
2018-10-26 10:12 ` [Qemu-devel] [PATCH 0/2] Deprecate the "collie" machine and Strongarm devices Peter Maydell
2018-10-27 11:04   ` Guenter Roeck
2018-10-29 13:24     ` Peter Maydell
2018-10-29 14:09       ` Guenter Roeck
2018-10-29 15:03         ` Philippe Mathieu-Daudé
2018-10-29 20:24           ` Guenter Roeck
2018-10-29 22:17             ` Philippe Mathieu-Daudé [this message]
2018-10-30  9:17         ` Markus Armbruster
2018-10-31 18:46       ` Thomas Huth

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=034785b2-0126-e480-2f3f-2295152b11ae@redhat.com \
    --to=philmd@redhat.com \
    --cc=armbru@redhat.com \
    --cc=linux@roeck-us.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).